Versioning by SVN RevisionsWe could just build SVN and upload it, tagged with the revision number. This is the easy way out. Versioning by FeaturesStart at 1.0. Increment 0.1 for every revision with a minor bugfix or feature change. Increment 1.0 for major revisions/feature changes. We could even do something like label odd numbers (1.0) as frozen, stable releases (only being fixed if bugs arise) and label even numbers (2.0) as the development/testing release.
|
Sign in to add a comment
If you go for the even/odd formula, try to do even as stable, odd as unstable. That's what the Linux kernel did (and perhaps still does, dunno). No sense in confusing people.
Yes, the linux kernal still does that. I think that the svn idea works just fine. Its easy to keep track of and no stupid errors like is it 2.0.1 or was it 2.1.0?
The linux kernel hasn't done that for about five years BTW. http://en.wikipedia.org/wiki/Linux_kernel#Version_numbering
Cyndia seems to be using svn # + number of local patches for its versioning.