What I usually do is to release in JIRA before the actual release (you can always change the date later in jira) so that I can build the release notes and download page using the informations in jira. As James said, when you release in jira, all the versions not fixed are put under the next version to be released. And I disagree that only resolved issues should have a fix version, as this is the way you can track a roadmap ...
On Thu, Sep 4, 2008 at 4:27 PM, James Strachan <[EMAIL PROTECTED]> wrote: > 2008/9/4 Gary Tully <[EMAIL PROTECTED]>: >> I want to do a 5.2 release. > > Yay! > >> There are 189 open issues with a fix >> version of 5.2 [1]. As these issues show up in the release notes[2], I >> think they should all be marked as fix version 'unknown' until they >> get resolved on trunk, in which event they again get a fix version. Am >> thinking that only resolved issues should have a fix version. >> >> comments? > > Yeah - when you actually do the release in JIRA, it moves all issues > with a fix for 5.2 to the next available release. So you might as well > just wait until we vote on the distro, then let JIRA do all the hard > work for you > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://open.iona.com > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
