Karl Guggisberg <[email protected]> writes: > Hi Sebastian > > Absolutely. That's one of the things we should do in the next release: > * proper release naming > * proper labeling in SVN > > I came up with a slightly different naming scheme, though. If we want to > be understood by users with less technical background a release name > "0.10.1-r1566" could be quite cryptic.
I don't think the revision number needs to be part of the version number. Otherwise what is the point of sticking another number in front of it? We are not planning to make a release with every commit. The revision could be displayed in the About dialog. Also, I think a major and a minor version is enough. If it should really become necessary to fix a tested version we can stick a patch version number on it. For development I think it is best to stick with revision numbers. > Why not simply call it "2010.01" (first release in 2010), 2010.02, > etc. ? There won't be more than 4 releases a year anyway. I don't > really see the need for a version number with three levels of > increments. See for instance Ubuntu release numbering: > https://help.ubuntu.com/6.10/ubuntu/about-ubuntu/C/version-numbers.html Personally, I don't like those year based version numbers. IMHO they only make sense if you follow a strictly yearly schedule. Matthias _______________________________________________ josm-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/josm-dev
