-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Aug 13, 2008, at 1:53 AM, Martin v. Löwis wrote:
Because there won't typically be sufficient testing and release
infrastructure to allow arbitrary bug fixes to be committed on the
branch. The buildbots are turned off, and nobody tests the release
candidate, no Windows binaries are provided - thus, chances are very
high that a bug fix release for some very old branch will be *worse*
than the previous release, rather than better.
Second, I don't think this is true. People using those patch
level releases will test and report bugs if they are introduced
by such backports.
They might be using releases, but they are *not* using the subversion
maintenance branches. Do you know anybody who regularly checks out the
2.4 maintenance branch and tests it?
So at best, people will only report bugs *after* the release was made,
meaning that there is a realistic chance that the release itself
breaks
things.
Sure, but this is just as true for security fixes. The only thing the
policy buys us is fewer /possibilities/ of breakage. I'm not
discounting that as worthwhile, but qualitatively, there's no
difference between non-security fixes and security fixes, as far as
our Q/A process goes.
My problem is that this backporting is not systematic. It's arbitrary
whether patches get backported or not. Part of the problem is that
it is/was also unclear whether there ever will be another release made
out of 2.4. When 2.4.4 was released, Anthony announced, in
http://mail.python.org/pipermail/python-dev/2006-October/069326.html
"This will be the last planned release in the Python 2.4 series"
So anybody committing to the 2.4 branch after that should have
expected
that the patches will never get released.
There's a difference between never being released, and unavailable in
the source repository.
- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSKNiEXEjvBPtnXfVAQIQgAP6A84mpv0JUkP4Z904TzoYDuqb3OtCNBMc
wo+VGw00p9JJ0f4lWRmXSkimtLNe1xoOj0/qhYXBa64P7ti3oa9Wo4VHCK/N0IcW
p8vXvhMG9sIhYrGb2cWDc4d/UA0kQqBPp3srtXwEumoWQbScH0zJHM7llX10unJ1
UfTST6Tof/s=
=ilvh
-----END PGP SIGNATURE-----
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
