On 3 February 2011 17:44, Guillaume Nodet <[email protected]> wrote: > Not sure it's related. Your filter is about opened issues, I'm only > talking about 0.3. > > The problem is that we have currently 18 issues that are marked as to > be fixed in 0.3, which isn't possible since it has been released: > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=fixVersion+%3D+%220.3%22+AND+project+%3D+ARIES+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC >
OK, collectively we've worked this down to zero now. I've also gone through the issues which were unresolved/closed to see if any had in fact been closed off. There was one which I've marked as resolved. I decided to go through them manually rather than have JIRA do the default thing of move them to the next version. So JIRA issues is now clean and ready for the 0.3 release to be closed. > Usually, we use JIRA to build the release notes and part of the > release process should imho flag the jira version as released and move > any remaining open issue to the next version (or to no version). This > is done in just one operation on JIRA by releasing that version. > How do users know what has been fixed in 0.3 if the JIRA don't > correctly reflect the state? > > So I think we should (for the future): > * make sure when we release something, all bugs in JIRA are up to date > * include some real release notes based on JIRA (I think > http://aries.apache.org/downloads/releasenotes.html is not really > sufficient) > * mark the JIRA version as released (which will move any still > opened issue to the next release) > * those release notes on the wiki (jira automatically creates a list > of solved issues for a release) > * send a proper announcement on the users list (and maybe [email protected] too) > > That's also to relate to the release cycle discussion we have .... ;-) > > > On Thu, Feb 3, 2011 at 18:24, Jeremy Hughes <[email protected]> wrote: >> On 3 February 2011 15:19, Guillaume Nodet <[email protected]> wrote: >>> This hasn't been done, but it seems there are still open issues >>> scheduled for 0.3 in JIRA, so that's a bit of a problem ;-) >> >> Please see mail I just sent about a shared filter I've set up so >> everyone can see which issues they have assigned to them and hence >> which ones they might be able to move to resolved. >> >>> >>> -- >>> Cheers, >>> Guillaume Nodet >>> ------------------------ >>> Blog: http://gnodet.blogspot.com/ >>> ------------------------ >>> Open Source SOA >>> http://fusesource.com >>> >> > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com >
