I didn't mean X as a character, just any number...eg 0.6.1, 0.6.9. Something to distinguish from the release without burning up minor version numbers.
I think most of our releases incorporate enough change to deserve a minor version bump, and I like them being consecutive....something about 0.6, 0.8 just doesn't sit right with me, but burning micro's is fine...yes its oddball of me ;) Robbie > -----Original Message----- > From: Andrew Stitcher [mailto:[email protected]] > Sent: 22 December 2009 18:39 > To: [email protected] > Subject: RE: Release numbering suggestion > > On Tue, 2009-12-22 at 18:24 +0000, Robbie Gemmell wrote: > > I would be for this if we move to major.minor.micro versions. That > would let us e.g. tag trunk as 0.6.X following the 0.6 branch then go > with 0.7.0 for our next release. > > > > I think in practice 0.6.x is already what we do in terms of scm tags. > However re actual embedded release versions we have to use actual > numeric values, at least for autotools we do - so I assume this is a > requirement. > > But perhaps I didn't exactly understand what you are suggesting. > > Andrew > > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
