- This topic has 2 replies, 2 voices, and was last updated 19 years, 3 months ago by
.
-
Posts
-
G’day,
A suggestion concerning version numbers for the beta releases – would it be possible to include in the release note / announcement the version number of the release? eg. 4.0M3 == 3.9.310
If you choose to upgrade via the update site, all you see is the internal version number, and I always do a double take when I expect to see 4.0M3, but instead see 3.9.310. I end up double checking which version I’m currently running (eg. 4.0M2 == 3.9.210) and making sure that the new version is indeed a newer version, but that’s a time consuming step that could be eliminated if the version number was shown somewhere in the release note (it doesn’t have to be in a prominent location – anywhere in the release note would do).
Cheers,
PeterPeter,
Sorry about the trouble, Eclipse only allows for numerical (a.b.c) versions, so the internal versions will likely stay while we continue to refer to them externally by Milestone numbers.Eclipse does something different that we don’t like, they call every single release “3.1” or “3.0”, so there is no way to tell the difference except by checking the Build ID.
I understand the Eclipse numbering limitation – that’s why I suggested putting the mapping between real version numbers (eg. “4.0M3”) and the Eclipse version numbers (eg. “3.9.310”) in the MyEclipse release note / announcement. That way I wouldn’t have to go and manually figure out the mapping myself.
Cheers,
Peter
