Opened at 2020-08-30T15:30:45Z
Last modified at 2021-03-30T18:40:19Z
#3400 new task
Cut an incremental release (2020-09)
Reported by: | jaraco | Owned by: | meejah |
---|---|---|---|
Priority: | normal | Milestone: | soon |
Component: | unknown | Version: | n/a |
Keywords: | Cc: | ||
Launchpad Bug: |
Description
To reduce the risk of introducing many Python 3 porting changes in a single release, the Python 3 porting team would like to cut an incremental release from master in the month of September to include the pending changes for a still Python 2-only release.
The Python 3 changes are meant to be compatible so should not have user-facing effects, but it would validate that the existing changes are indeed compatible. I understand there are a few features as well that would be included in this release.
warner, I understand you may be able to cut the release. We're aiming for anytime before the end of September. Please let me know if I can help.
Change History (5)
comment:1 Changed at 2020-08-30T15:31:06Z by jaraco
- Type changed from defect to task
comment:2 Changed at 2020-09-14T13:09:41Z by exarkun
- Owner changed from warner to meejah
comment:3 Changed at 2020-09-14T21:36:00Z by warner
heya.. I can cut a release, I'll aim for next weekend. Any particular commit ID I should aim for?
comment:4 Changed at 2020-09-15T19:23:37Z by exarkun
It should be fine to do whatever master@HEAD is at the time. Thanks!
comment:5 Changed at 2021-03-30T18:40:19Z by meejah
- Milestone changed from 1.15.0 to soon
Ticket retargeted after milestone closed
warner has the keys to sign a release but I don't expect he'll actually do the rest of the release engineering.
meejah did the previous release, perhaps he will do the next one.