-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Preparing release version 4.6.9 #6391
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
See also #6392 to update the copyright year to 2020 for the 4.6 branch. |
I'll wait until resolution 🕥 |
Sorry, what do you mean by "resolution"? |
what ya'll decide on the copyright year shenanigans :) |
Oh I see, thanks! 😁 |
Legally? I have no idea. Practically? Some of them were out of date for a few years already. Functionally? It doesn't make much difference. |
Thanks! We'll the copyright pr has been merged, so all this needs is a rebase. 👍 |
Thanks @asottile!
Perhaps this wording might be misinterpreted (if you were planning on saying something like this on twitter/announce), given that while we will no longer backport patches ourselves, we will still keep 4.6-maintenance around, and make releases based on user-provided patches. |
ah yeah I was planning on being a little more tactful :) |
Merge pull request #6391 from asottile/release-4.6.9
Shall we do the last core-supported python 2.x release?