Greg Reddin wrote:
On Nov 30, 2005, at 11:21 AM, Don Brown wrote:
But back to the topic, what do folks think of the proposal to target
tickets to milestones and use them for release planning?
+1. It's basically just a formalization of what we do on the wiki now,
right?
Kinda. When we get close to a release, we take the open bugs from bugzilla and
try to close or resolve them. This approach would supersede the need for this
by providing a list of open bugs at any stage in the cycle. Furthermore, our
release plan only covers outstanding bugs, and not enhancements. When we want
to declare we won't address a bug in this release, we mark it as later. I'd
much prefer we mark even bugs against a milestone to know 1) what we are
committed to fixing and 2) when it will be fixed.
And a big thank you for the +1's :) Any more?
Don
I think we should start immediately by creating upcoming milestones,
and going through all our old tickets and assigning them to the new
milestones. This would go a long way to folks wondering what exactly
was in 1.3.0.
+1
Greg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
