Guido van Rossum <guido python.org> wrote:
> IMO it's the call of the release managers. Board
members ought to
> trust the release managers and not apply undue
pressure.
+1, but I would love to see a more formal definition of what
a "bugfix" is,
which would reduce the ambiguous cases, and thus reduce the
number of times the
release managers are called to pronounce.
Other projects, for instance, describe point releases as
"open for regression
fixes only", which means that a patch, to be eligible
for a point release, must
fix a regression (something which used to work before, and
doesn't anymore).
Regressions are important because they affect people wanting
to upgrade Python.
If something never worked before (like this unicode path
thingie), surely
existing Python users are not affected by the bug (or they
have already
workarounds in place), so that NOT having the bug fixed in a
point release is
not a problem.
Anyway, I'm not pushing for this specific policy (even if I
like it): I'm just
suggesting Release Managers to more formally define what
should and what should
not go in a point release.
Giovanni Bajo
_______________________________________________
Python-Dev mailing list
Python-Dev python.org
ht
tp://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/p
ython-dev/nessto%40sharedlog.com
|