[Tracker-discuss] Feature/Change request handling procedure

["Martin v. Löwis"]

Stefan Seefeld schrieb:
> 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.

Ah, ok. I'd say it makes no sense. The Python project has a single
milestone at the moment: Python 3000. It didn't have any milestones
before (perhaps Python 2 was one, as well), and it may not have any
milestones afterwards.

There really isn't any "planning" of features. Features get added when
there implementation is complete; it's not that people stop working
on something and work on something else just because it is deemed
more important.

Even priorities are largely irrelevant. Contributors have their own
views of what issues are important; some value backwards compatibility
and put efforts into *not* adding new features (because they fear
incompatibility), others value reliability of the interpreter and
fixes reported ways of crashing the interpreter the day those are
reported.

Regards,
Martin