[Tracker-discuss] Feature/Change request handling procedure
seefeld at sympatico.ca
Sun Nov 26 23:38:05 CET 2006
Martin v. Löwis wrote:
> Stefan Seefeld schrieb:
>> This is why I see milestones almost *defined* by the list of bugs they
>> contain: instead of assigning due dates to bugs, you define a milestone
>> to be reached once a set of bugs is fixed.
>> This is what I used in other projects, and I thought it might work
>> well in python-dev, too.
> I can't see how: what would examples for milestones be? You seem
> not to be talking about releases here. If not, what is the purpose
> of having milestones in the first place?
If you define milestone 1 .. milestone N, and assign issues to them,
this is a way to prioritize issues, and a way to measure how close you
are to the next milestone. 'X issues left before the next release' is
useful information to have, isn't it ? Of course, you can attach more
to a milestone (such as an ETA).
I only introduced it as a suggestion to replace numerical priorities.
Whether this makes sense for your development process is something I
can't judge at all.
...ich hab' noch einen Koffer in Berlin...
More information about the Tracker-discuss