[MonoDevelop] Best way to manage program version number for C
Matias Wald
waldmatias at hotmail.com
Sun Apr 10 21:56:34 EDT 2011
Hi Steve,
Not sure on MonoDevelop rules for incremental numbers with C, but I can tell
you that linking compilation to minor version number is not the the way to
go (that's why there's a build or revision numbers).
Versioning standards go like this:
[MAJOR].[MINOR].[BUILD].[REVISION]
Rules for numbers (we use this):
Major & Minor versions map to new GUIs, new features, new components and new
system-wide enhancements.
Minor versions map to bug fixing (general) and component-wide enhancements
(not major)
Build versions map to specific system-wide compilations. Generally, when
QC/QA approves a release (which maps to a build), that build may be used as
a public release.
Revision versions map to system-wide compilation. These are incremental for
each compilation.
I hope this helps,
Matias
--
View this message in context: http://mono.1490590.n4.nabble.com/Best-way-to-manage-program-version-number-for-C-tp3440476p3440833.html
Sent from the Mono - MonoDevelop IDE mailing list archive at Nabble.com.
More information about the Monodevelop-list
mailing list