On Wed, Jan 6, 2016 at 7:06 PM, Martin Panter <vadmium...@gmail.com> wrote:
> Currently some SSL tests in the test suite are broken by a recent > certificate change at https://svn.python.org/; see > <https://bugs.python.org/issue25940> for the bug report. The tests are > broken when the test suite is run with the “-unetwork” option enabled, > and most of the buildbots appear to be affected. (In 3.6 the tests > have temporarily been disabled as a workaround.) I have a simple patch > that subsitutes the old root certificate for the new which I would > like to commit, but I’m not sure which branches to apply it to, or > even which branches are open to normal maintainence and bug fixes. > > According to Larry > <https://mail.python.org/pipermail/python-dev/2015-December/142566.html>, > 3.4.4 was the last bug fix release for 3.4, so I assumed the 3.4 > branch should now be in security-fixes-only mode. However this branch > still seems to get a lot of non-security action, for example the most > recent bunch of changes were some work on the provisional “pathlib” > module. So firstly I would like some clarification on the status of > 3.4 and what its future is. > To me Larry's email mainly indicates that we're not going to do more binary releases in the 3.4 branch. The work I did on pathlib is probably never going to be released in that branch -- but since I merged it into 3.5 it's not going to waste, and the effort was pretty minimal. (And people *could* still pick it up from the source.) > Secondly, I would normally say a fix for the test suite isn’t really > appropriate for the older security branches. But in the bug report, > Koobs specifically requested this be fixed in 3.4 and possibly earlier > branches as well. What do others think about this? > It should definitely be fixed in 2.7, 3.5 and 3.6. If you want to do it in 3.4 too that sounds totally fine (it's just one extra merge). Are there still any active buildbots for 3.4? The question is, why? I guess one reason might be to ensure that if we *do* have to do an emergency release of 3.4 (it's always a possibility), it would be easier if the tests were all known to be passing, otherwise doing a release (even a source-only release) would be a big hassle. OTOH if we don't make changes the tests will generally not start failing -- the current issue notwithstanding. :-) So if buildbots are a scarce resource it's fine to repurpose them for more recent releases. Oh, finally. I'm eager to answer this but I'm not actually the best resource here -- I'm pretty rusty where it comes to our build and test practices. -- --Guido van Rossum (python.org/~guido)
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
