Shall we retroactively create a 0.5 tag for future usage? Andrews suggestion of looking at the .svnrevision file doesn't work for 0.5 as it reports HEAD.
I just noticed from the users list why Rajith wanted to know the revision, and he understandably got the wrong revision from looking at the 0.5-release branch. It doesn't change the outcome discussed as no code was changed, but the noted rev 779632 was actually an error on my part after 0.5 was produced (due to a partially-switched SVN checkout) and 0.5 was released at rev 775777 as far as I can tell. Robbie > -----Original Message----- > From: Andrew Stitcher [mailto:astitc...@redhat.com] > Sent: 06 January 2010 21:26 > To: dev@qpid.apache.org > Subject: Re: Tagging our releases > > On Wed, 2010-01-06 at 15:29 -0500, Rajith Attapattu wrote: > > I was just trying to quickly figure out the svn rev the Java 0.5 > > release and found that there wasn't a tag available for it. > > (please note we do have a branch for it, but I still think we should > > be tagging the final release). > > It seems we have tags for the previous releases (all though some > > aren't explicitly named). > > > > I thinks its good practise to tag releases. Some of the previous > > releases even had tags for RC's as well. > > So lets make sure we tag the final release for 0.6 > > I fully intend to tag the 0.6 release when I make it. > > However note that you can find a releases svn revision by looking in > the > *.svnrevision file in the distribution directory - obviously this is > not > massively convenient. > > Andrew > > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
