On Fri, Jul 25, 2008 at 10:25 AM, Gordon Sim <[EMAIL PROTECTED]> wrote:
>> 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. In general I agree with this, but I think moving it to unassigned should be an active step, that way somebody has at least looked at the issue and gone "nah, not urgent" and (ideally) set the priority etc corrrectly. The problem was there was a heap of stuff which was just kind of sitting around... We probably need to define our Jira handling process a bit more tightly, particularly with ones regarding potential security issues (other than making the Jira private until a patch is released) >> 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. Righty ho. :) - Aidan -- Apache Qpid - World Domination through Advanced Message Queueing http://cwiki.apache.org/qpid
