[Tracker-discuss] Feature/Change request handling procedure
"Martin v. Löwis"
martin at v.loewis.de
Sun Nov 26 09:55:29 CET 2006
Paul Dubois schrieb:
> I think the design discussion of 'milestone' tells us that we don't yet
> know what we want so we should push that back to 'phase 2'. FWIW
> certainly we set the due date from the issue; we have a meeting, decide
> what goes in the next release, and the group leader goes and sets the
> due date, or sets it after conversing with the assignee.
Just as I wrote to Erik: in Python, we don't set due dates. It's all
volunteers, so you can't force anybody to do something by a certain
Even release plans follow that principle: the release (alpha, beta, rc,
final) is on a scheduled date; what is done by that date is done, what
isn't, is not done. So if somebody misses beta1, the new feature has
to wait for the next release.
> Let's be minimal and fast on this first go.
That is very reasonable. So far, we have used something like
"target milestones" only during releases so far, and the next
release is well ahead (late 2007, early 2008; 2.5.1 will be
released earlier, but we won't have new features in it).
More information about the Tracker-discuss