Development Team/version scheme
(New page: The version scheme currently used by DareNET Development Team projects is as follows: '''MAJOR.MINOR.PATCH [BUILD/REVISION]''' * '''Major''' indicates that the code base has been complet...) |
m |
||
| Line 8: | Line 8: | ||
* '''Build/Revision''' is the SVN revision number, along with the date the program was built ''(used mostly for debugging purposes)''. | * '''Build/Revision''' is the SVN revision number, along with the date the program was built ''(used mostly for debugging purposes)''. | ||
| - | Branches are created for every minor release | + | === SVN Notes === |
| + | |||
| + | * Branches are created for every minor release. | ||
| + | * Trunk contains the latest development version. As such, trunk occasionally "breaks" (doesn't compile, or fails functional tests). | ||
Current revision as of 05:57, 15 April 2009
The version scheme currently used by DareNET Development Team projects is as follows:
MAJOR.MINOR.PATCH [BUILD/REVISION]
- Major indicates that the code base has been completely rewritten/refactored, or significant changes have been made that introduce backward incompatibility.
- Minor indicates an addition of features.
- Patch indicates a fix (e.g. bug fixes, or changing internal structure without impacting functionality).
- Build/Revision is the SVN revision number, along with the date the program was built (used mostly for debugging purposes).
SVN Notes
- Branches are created for every minor release.
- Trunk contains the latest development version. As such, trunk occasionally "breaks" (doesn't compile, or fails functional tests).
