Add docs page about plans for dropping py27 and py34#4646
Conversation
866adbf to
e2a9aaf
Compare
Codecov Report
@@ Coverage Diff @@
## master #4646 +/- ##
==========================================
+ Coverage 95.71% 95.73% +0.02%
==========================================
Files 111 111
Lines 24761 24761
Branches 2454 2454
==========================================
+ Hits 23701 23706 +5
+ Misses 747 745 -2
+ Partials 313 310 -3
Continue to review full report at Codecov.
|
|
Hi @KengoTODA, Shouldn't the rtd-bot post a link on this PR to the built documentation? 🤔 |
|
@nicoddemus the HEAD of this PR comes from other repo, so RTD cannot build based on changes in this PR. So, to use rtd-bot, the HEAD of PR should exist in the same repo. |
|
Ahh I figured as much, thanks. 👍 |
|
|
||
| **After 2020**, the core team will no longer actively back port-patches, but the ``4.x-maintenance`` | ||
| branch will continue to exist so the community itself can contribute patches. The | ||
| core team will be happy to accept those patches and make new ``4.X`` releases **until mid-2020**. |
There was a problem hiding this comment.
@RonnyPfannschmidt I've added mid-2020 here just to have some end date. What do you think?
There was a problem hiding this comment.
@nicoddemus the devil on my shoulder just wants to make the deprecation warning more and more passive aggressive with each release - as long s the release pipeline is accessible the effort to cut a release can be downsized to something nicely manageable
There was a problem hiding this comment.
No problem with the warnings, I wonder though if we want to declare a final date where we are no longer obligated to make 4.X releases anymore (even if we still do occasionally)
There was a problem hiding this comment.
i believe we have about 9 months of active support (2.7 gone form mainline vs 2.7 eol), i think having a 6 month grace period after that to do releases from our side is fine, afterwards its the end of line from our side, no more releases but we should still merge to the maintenance branch in good faith (people have to manage their setups on their own then)
There was a problem hiding this comment.
Agreed.
OK to merge this then?
Fix #4635