On Sep 26, 2019, at 14:50, Ethan Furman <et...@stoneleaf.us> wrote: > > On 09/26/2019 09:28 AM, Brett Cannon wrote: >> Steve Dower wrote: > >>> The biggest thing that will change is that all our CI systems will stop >>> testing 2.7, and there's a good chance we'll lock (or delete?) the 2.7 >>> branch from our repo. >> A final tag of the branch will be made and then the branch will be deleted >> (it's how we handle all EOL versions). > > Will there be a time delay between the final tagging and the deletion so any > who would like the repo in its final state can clone it at that point?
Nothing will be lost, there's no need for a time delay. As we do for every release, there will be a tag created for the final 2.7 release of the form "v2.7.xx". That allows you to checkout the state of any release, including the final 2.7 release. At end-of-life time, we will also create a final "2.7" tag that reflects the final state of the 2.7, in case anything else was checked in following that last release. There will no longer be a "2.7" branch in the repo so it won't be possible to merge 2.7 changes back into the central repo. The 2.7 tag will act as sort of a read-only branch, i.e. you can still do: git checkout 2.7 to access it. If you want, you could create a local branch in your repo. See: https://devguide.python.org/devcycle/#end-of-life-branches -- Ned Deily n...@python.org -- [] _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/WVRXP5AVIOUUHQH2ZZ4RLXYRPOJWFFNT/
