Re version numbers and RPM versions etc. I have a proposal.
Daniel Kulp wrote:
On Tuesday 06 March 2007 17:15, Alan Conway wrote:
On Tue, 2007-03-06 at 17:03 -0500, Daniel Kulp wrote:
Just FYI: that needs to be changed before the release. If the
artifact doesn't have "incubator" in the name, it will get a "-1".
That's the main reason the maven versions are all "1.0-incubating-M2".
I'd like to propose that we adopt a numeric "logical" version.release
scheme for all releases but also designate them by an apache M number.
So M1 == 0.1, M2 == 0.2 (or 0.9 if we want to play games) etc. Once we
get out of incubator we drop the M numbers and continue the simple
version.release numbering.
For RPM purposes we need to use the simple numeric version.release up
front so rpm can figure out the ordering, but I think we can safely add
a decorator to meet the apache requirement (RPM experts can you
confirm? I checked the rpm source code and it appears that RPM will stop
at the first differing segment so e.g. 0.2-incubatingM2 is older than 0.3)
So the RPM versions would be:
0.1-incubating-M1
0.2-incubating-M2 (or 0.9-incubating-M2 or 0.9-incubating-M9 at our whim)
etc. till we leave incubator and go to 1.0 etc.
It would be simplest to have a straightforward correspondence between
0.x and Mx but they don't have to be related provided they both increase
monotonically on every release.
Cheers,
Alan.
