Thanks Justin. Speaking with others, I think we should definitely target maven artefacts as part of our release distirbution for 0.10.
All - are we in shape for this i.e. do the maven artefacts create-able from the build work ok/include the correct dependencies ? I haven't tried them, but iirc others have ? Thanks & Regards, Marnie On Thu, Feb 3, 2011 at 10:27 PM, Justin Ross <[email protected]> wrote: > Hi, everyone, and happy Chinese new year! It's time for an update on > the qpid 0.10 release. > > The schedule: > > 16 Feb > > - Alpha > - Trunk remains open > - Feature integration ends > - The alpha release tests the release process after the > introduction of major features > > 2 Mar, 2 weeks later > > - Beta > - Branch for release (trunk remains open) > - Release branch commits require approval > - Release manager produces outstanding bug report, triages bugs > > 16 Mar, 2 weeks later > > - RC1 > > 23 Mar, 1 week later > > - RC2 > > 30 Mar, 1 week later > > - RC3 > - Targeted release date > > I'm using the following jira query (fix version 0.9, issue type either > new feature or improvement): > > > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+QPID+AND+issuetype+in+%28%22New+Feature%22%2C+Improvement%29+AND+fixVersion+%3D+%220.9%22+ORDER+BY+status+DESC%2C+priority+DESC > > About two weeks remain before the feature integration window closes, > and I'd like to start getting feedback about the items in that list. > > To begin, however, the list itself needs some maintenance: > > - There may be some things here that don't rise to the level of > "major release trackable"; if so, I can adjust the query I use or > modify the issue itself > > - If you are developing a major feature or improvement, it should be > represented by a jira on this list > > - There are three unassigned items; if nobody adopts them, I suggest > we set their fix version to 'future' > > - In general these should have their due date set to 16 Feb; we > should discuss exceptions for items that don't threaten to > destabilize the codebase > > ("Hey, dude. Why 16 Feb, in the middle of the week?" My thinking > there is to to leave the latter half of the week to absorb any > minor delays, and--one hopes--avoid extending any work into the > weekend.) > > At the same time, I'd like to request that the assignees begin to > provide some feedback in the jira comments. Specifically, I'm looking > for: > > - Will it be feature complete (and ready to land if it's on a > branch) by Feb 16? > > - Characterize its current degree of completion > > If you don't think it will be ready in time, we need to hold a brief > discussion about it on the mailing list. > > I plan to do another release update next week, and every week after as > we approach the release dates. (I ought to research alternative > calendars, to see if I can't hit another new-year boundary.) > > Finally, if anyone has comments for me, especially concerning anything > I should be keeping track of that I'm not, please raise them. > > Thanks, > Justin > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > >
