On Mon, Oct 12, 2009 at 5:32 PM, Tom Berger <[email protected]> wrote: > 2009/10/12 Jonathan Lange <[email protected]>: >> On Mon, Oct 12, 2009 at 5:15 PM, Graham Binns <[email protected]> wrote: >>> 2009/10/12 Jonathan Lange <[email protected]>: >>>> That's a good suggestion. It raises two questions, neither of which I >>>> know the answer to: >>>> >>>> - why would there open bugs on the milestone after we've frozen the code? >>> >>> Because there's a finite amount of time in a developer's day, and >>> sometimes we think we're able to get things finished but life gets in >>> the way. >>> >> >> I haven't been as clear as I ought. Sorry. >> >> In the plan I described, I had meant for the RM to go through the >> milestone at some time shortly after code freeze and move the bugs >> that are: >> a) on the milestone >> b) open >> c) not release critical >> >> off the milestone. I say "shortly after" to allow developers time to >> retarget the bugs themselves. >> >> My question, now that I think about it, would have been better phrased >> as "What's the point of having open, non-release-critical bugs on the >> milestone after code freeze?". I think the answer is "there is none". > > What I'm suggesting is that developers will take care to remove bugs > that have missed the milestone, and the RM (or whoever else has the > authority) sets the importance to Critical if it isn't already, if > they agree that the bug should be considered release-critical. >
Agreed. I'll do this. jml _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
