On Thursday 05 November 2009, CeDeROM wrote: > What is more - a 0.3.0 release is available already on the download > page (openocd 0.3.0 November 4, 2009) - is it 0.3.0 already or still > the 0.3.0-rc0? If rc0 why it is named 0.3.0? :-(
Current release is 0.3.0 ... I removed RC0 since I anticipated confusion, and anyone who really needs it can just grab the equivalent from git. We're not Linux; we don't need to leave release candidates around. Agreed, release numbering is teh suxxor. As you noted, two of the digits are effectively meaningless. Changing it for this release was not in the cards. However ... the January release could change that. I kind of like the U-Boot release naming scheme ... "v2009.11" for this month's release-to-be. "v2009.11-rc1" for the first release candidate (9 days ago, FWIW). Also, I'd like to see "openocd -v" report a version code that directly corresponds to some "git describe" output even during the merge window. Fixing that requires changing the release numbering scheme... - Dave p.s: > Why don't we name a release 0.3.0, make it public, fix errors for a > week, release 0.3.1, fix errors for next week then release 0.3.2, if > there are no errors add some features and release 0.3.3... I don't recall ever seeing any project which works that way. Micro version numbers are for bugfix releases. At any rate, for as long as this project has documented how it numbers its releases, that has *NOT* been the scheme it uses. > if there > are releases where only the middle number changes, why to use others? Right; we don't use major or micro, so there's IMO no point in having them be part of every release. > By the way - is 0.3.0 supposed to be an unstable release while the > 0.4.0 is the next stable release (as in Linux kernel numbering)? Ever since 2.6 came out, Linux abandoned that scheme. That's quite a few years ago now. You need to be more current. :) > Is > all these numbers really necessary? Does anybody have control over > these numbers? If the community wanted, we *could* fix this mess for the upcoming release... _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
