DevelopmentProcess

From WeBWorK_wiki
Revision as of 12:02, 9 March 2013 by Djun Kim (talk | contribs) (Created page with "== WeBWorK Development Process == The WeBWorK development community uses http://github.com to manage distributed development. Development of WeBWorK follows a model which en...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

WeBWorK Development Process

The WeBWorK development community uses http://github.com to manage distributed development.

Development of WeBWorK follows a model which enables support of legacy versions, maintenance of a stable version, and an active development of new features for which will eventually become the new stable version.

At a moment in time, the github repository will have multiple legacy branches, a single stable branch, and a single development branch.

Legacy branches will receive security fixes only.

Development of the stable version will be restricted to bug fixes and minor features.

Development of major features will be carried out on the development branch.

In general be no backporting of features to legacy versions.

Work done on the development branch may break compatibility with previous versions of APIs, database schemas, etc; upgrading from a stable to a new version will generally require migration of existing configurations and data.