General version rules

From ScorecWiki

Jump to: navigation, search


Version Numbering

Version numbers should be meaningful. A good scheme is to number each version A.B.C, for example 2.1.4. A represents major feature changes, B represents minor feature changes, and C represent bugfixes, documentation updates, and performance improvements. So, for example the first version of a library or program could be 0.1.0.

You can also specify a particular version number as a milestones, such as:

Alpha 1

Earliest development version.

Alpha 2 Version

Better candidate for release than alpha 1, but may still be lacking some features and have some bugs.

Beta Version

Candidate for release. Software is feature complete but may still need some testing for bugs.

Release Version

The version is open to the everyone and is posted on SCOREC website.

Personal tools