Aidan Skinner wrote:
following what I think was a pretty sucesful Jira clean up, it's possible to get a better grip on M3. There are currently 143 outstanding bugs against it, 3 of which are blockers and 2 are criticals. I've tried to assign as many of the 'unassigned' pile (which was very, very large) to somebody appropriate as possible so there's at least an owner. I think we should get default component owners set up, I'd be happy to take the .Net client for instance.
I'm willing to volunteer for dealing with the c++ client & broker issues. However it does strike me that having some Jiras unassigned can actually be useful. It allows you to see what is being worked on and which issues are waiting for someone to take them on.
Obviously if no-one is assigned to a particular issue its less likely that its going to be addressed for M3. I've been through the c++ issues marked as 'fix for M3' to make sure everything there is assigned. (Theres one issue that isn't, QPID-783, that I believe can now be resolved and I'm chasing that up and will either resolve it or assign it by the end of the day).
Given we're around a fortnight away from freezing for M3, it occured to me that nobodys stepped forward for release manager duty. I'm happy to do it again, M2.1 wasn't that bad (or I've clearly supressed the more traumatic memorys). Objections?
None whatsoever! Thanks very much Aidan, if you are willing to do this again that will be greatly appreciated.
