This is just an idea. Instead of using NO-JIRA we could create a JIRA for 0.12 and then use that for all administrative commits related to 0.12 Ex. creating the branch, creating tags or even use that as a secondary JIRA when porting changes from trunk to release branch.
The advantage here is, that there is a single place which gives you a list of all the (administrative) commits related to a particular release. It certainly provides a nice audit trail and gives the release manager an easy way to keep track of all changes going into the release branch. Regards, Rajith On Thu, Jun 30, 2011 at 10:02 AM, <[email protected]> wrote: > Author: jross > Date: Thu Jun 30 14:02:01 2011 > New Revision: 1141543 > > URL: http://svn.apache.org/viewvc?rev=1141543&view=rev > Log: > NO-JIRA: Branch for the 0.12 release > > Added: > qpid/branches/0.12/ (props changed) > - copied from r1141493, qpid/trunk/ > > Propchange: qpid/branches/0.12/ > ------------------------------------------------------------------------------ > --- svn:mergeinfo (added) > +++ svn:mergeinfo Thu Jun 30 14:02:01 2011 > @@ -0,0 +1,3 @@ > +/qpid/branches/0.5.x-dev:892761,894875 > +/qpid/branches/0.6-release-windows-installer:926803 > +/qpid/branches/java-network-refactor:805429-825319 > > > > --------------------------------------------------------------------- > 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]
