From: David Abrahams (dave_at_[hidden])
Date: 2007-11-06 00:44:05
on Mon Nov 05 2007, Rene Rivera <grafikrobot-AT-gmail.com> wrote:
> David Abrahams wrote:
>> That means establishing a 1.36.0 milestone
> There's no need to create such a milestone. I created the "To Be
> Determined" milestone.
Why is putting tickets in "to be determined" better than assigning
them to 1.36.0 until such time as we decide to do something else with
them? I don't like limbo.
> Which means that in addition to looking at the tickets currently in
> the 1.35.0 milestone we need to look through the ones in "To Be
> Determined" to see if any apply for this release. But ideally I
> would rather see the bug handling to occur entirely outside the
> 1.35.0 milestone
What does that mean? No bugs should be labelled as "must be fixed for
the release of 1.35?" How will we track our progress towards 1.35
> since all the bugs should be getting fixed in the
> trunk, not the release.
I don't understand what connection the area of the repository has with
> Hence as a gross approximation we would move all the 1.35.0 tickets
> to the "to be determined" milestone. And when a library is placed in
> the branch we can move the resolved tickets only to 1.35.0.
You're suggesting having all open tickets in "To be determined," and
only assinging milestones after they're closed? That doesn't seem
like a very good use of the technology.
-- Dave Abrahams Boost Consulting http://www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk