qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell" <robbie.gemm...@gmail.com>
Subject RE: Release numbering suggestion
Date Tue, 22 Dec 2009 18:24:40 GMT
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.

Robbie

> -----Original Message-----
> From: Andrew Stitcher [mailto:astitcher@redhat.com]
> Sent: 22 December 2009 15:44
> To: Qpid Dev List
> Subject: Release numbering suggestion
> 
> We currently have a problem distinguishing between the qpid release
> numbering for actual releases and release branches and code development
> on trunk.
> 
> For example before starting the 0.6 release the label 0.5 was ambiguous
> - it referred both to the development code on the and the code in the
> 0.5 release. By that I mean that the code on trunk thought it was 0.5
> too and reported that.
> 
> I propose that we change the trunk numbering to 0.7 at the point we
> branch 0.6 for release.
> 
> Then I propose that we change the numbering to 0.8 when we start the
> next release process.
> 
> Then we would change trunk numbering to 0.9 when branching the next
> release etc.
> 
> The advantage of this scheme is that it is immediately obvious whether
> a
> given release is development or a released release (odd numbers are
> dev,
> even are release). It also means that the numbering is never shared
> between trunk and a branch.
> 
> Minor disadvantage: Our releases skip from 0.6 to 0.8 to 0.10 etc.
> 
> Comments?
> 
> [unless I hear heated opposition by the actual point of release, I will
> do this]
> 
> 
> 
> 
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org



---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


Mime
View raw message