I changed the JIRA versions to SNAPSHOT and modified existing issues that referenced them. The current version of JIRA running in the shale space already has the "disable bulk email" feature. So this will come in handy when we bulk close our issues and change the version at the time of release.
I archived the old "NIGHTLY" version so we don't use it anymore. Unfortunately its not clear what to do with all of the issues left there. I've already taken care of the issues that are still open and had a affects version of NIGHTLY (changed those to 1.0.3-SNAPSHOT.) Its kind of weird that in JIRA you can't "find" an issue based on an *archived* version, although you can add the affects and fix version to your "issue navigator" and search on other criteria (and then sort on version by clicking the column.) Sean On 8/2/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
In the future JIRA will allow disabling of email just for bulk changes. In the meantime we might have to ignore the wave of emails that occur right before a release. I'll look into other options for limiting the email in the meantime. Sean On 8/1/06, Craig McClanahan <[EMAIL PROTECTED]> wrote: > On 8/1/06, Sean Schofield <[EMAIL PROTECTED]> wrote: > > > > I propose we change the JIRA versions to the way we now do it in MyFaces. > > > > Change the existing version 1.0.3 to 1.0.3-SNAPSHOT. Then after the > > release vote and testing we create a version 1.0.3. (and archive the > > old snapshot version.) We do a bulk change on issues resolved with > > version 1.0.3-SNAPSHOT and change to 1.0.3. > > > > So up until the release point, JIRA shows that issues were reported > > against 1.0.x nightly and fixed against 1.0.x nightly. Then the > > release is finalized and the versions are changed to reflect what got > > fixed in the final release versus what was reported during that > > release cycle but still not fixed. > > > > Sound good? > > > Works for me (although it sounds like a source of email storms). I don't > have a problem with the current approach either, though. > > Craig > > > Sean > > > >
