I've shuffled the issues around now, so that they're organised by rc release. I didn't bother with the previews.
On 25/11/2010, at 2:16 AM, Steve Ebersole wrote: > You have to reopen them, edit them and then close them. I have to do this > occasionally. It is a pain. But you can do all those actions in bulk which > helps a little. > > -- Sent from my Palm Pre > > [email protected] > http://hibernate.org > On Nov 24, 2010 2:37 AM, Adam Murdoch <[email protected]> wrote: > > > On 23/11/2010, at 8:36 PM, Scheper, Erik-Berndt wrote: > >> Hi, >> >> I'm having trouble finding out the issues fixed between 0.9 rc1 and 0.9 rc3. >> >> Usually I'd be looking in the JIRA changelog for this, but unfortunately >> every single change since 0.8 has been logged under release 0.9. This makes >> the changelog immense and unusable for most practical purposes. >> >> Is there a reason you're not keeping changelogs of individual milestone / RC >> releases? > > Not really. We never really intended for 0.9 to have any milestones or rc > releases, and so we started off marking issues as fixed in 0.9. However, JIRA > doesn't let you change an issue once it is closed, and so they stayed as > fixed in 0.9 even when we started doing the preview and rc releases. If it > were easy to move the issues into 0.9-rc-1, 0.9-rc-2 and so on, then I would. > > We will make sure milestones and rcs are tracked as separate releases in JIRA > for the releases after 0.9. > > > -- > Adam Murdoch > Gradle Developer > http://www.gradle.org > CTO, Gradle Inc. - Gradle Training, Support, Consulting > http://www.gradle.biz > -- Adam Murdoch Gradle Developer http://www.gradle.org CTO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz
