We had a similar discussion when 0.8 went out and the feeling was that issues completed during the development stream should be left marked as such because you cant have 2 fix-for versions when resolving a JIRA, and so only issues that were fixed after branching and updating the version would get fix-for as the release version.
Last time we released I generated some html release notes with the content from the 0.7 and 0.8 versions in JIRA and put them on the website. This allows organising them a little nicer in terms of what gets more prominence, and means the release email drives traffic to the website rather than JIRA (which also has a side effect of being faster for the users, since JIRA is often excruciatingly slow). Robbie On 10 March 2011 14:14, Gordon Sim <g...@redhat.com> wrote: > On 03/10/2011 01:50 PM, Marnie McCormack wrote: > >> Hi Justin/All, >> >> I'm wondering what the approach for identifying the content of the 0-10 >> release from JIRA is ? >> >> I've just been trying to figure out what is actually in 0-10 from JIRA and >> its not easy since we have 0-10 items complete adn I think raised during >> the >> release process and a load of open 0-9 items for which we can't tell the >> target release. >> >> We should be able to generate release notes from JIRA, so should we update >> all items in the 0-10 release to have a fix for version of 0-10 ? >> > > I marked the JIRAs I fixed for 0.10 as fix-for 0.9 (the 0.10 option was > only recently added). So I believe anything that is resolved and has fix-for > 0.9[1] can have the fix-for updated to 0-10. Anyone know if there is a way > to do this as a bulk update or similar? > > [1] > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520&version=12315382 > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > >
