Note that if we're going to have each component with its own release cycle (or even each bundle with its own release cycle), we need to have that reflected in JIRA and in the release notes. Currently, we've only used 0.2 or 0.3 in jira, but we'd have to use blueprint-0.4, etc ....
On Thu, Feb 3, 2011 at 20:51, zoe slattery <[email protected]> wrote: > Hi Guillaume - thanks for this, a couple of comments in line. >> >> 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 >> >> 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 > > yes - it would have been good to do this first >> >> * include some real release notes based on JIRA (I think >> http://aries.apache.org/downloads/releasenotes.html is not really >> sufficient) > > Yes - and we did for 0.2-incubating (although the link from the web site is > broken now), so this is the plan already. But, as I said before, > http://www.mail-archive.com/[email protected]/msg00343.html any help > would be appreciated :-) >> >> * mark the JIRA version as released (which will move any still >> opened issue to the next release) > > I think Jeremy is handling this >> >> * those release notes on the wiki (jira automatically creates a list >> of solved issues for a release) > > see above >> >> * send a proper announcement on the users list (and maybe [email protected] >> too) > > OK - I'll add it to the instructions >> >> 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
