Cut an incremental release (2020-09) #3400

Open
opened 2020-08-30 15:30:45 +00:00 by jaraco · 4 comments

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.

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.
jaraco added the
unknown
normal
defect
n/a
labels 2020-08-30 15:30:45 +00:00
jaraco added this to the 1.15.0 milestone 2020-08-30 15:30:45 +00:00
warner was assigned by jaraco 2020-08-30 15:30:45 +00:00
jaraco added
task
and removed
defect
labels 2020-08-30 15:31:06 +00:00

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.

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.
warner was unassigned by exarkun 2020-09-14 13:09:41 +00:00
meejah was assigned by exarkun 2020-09-14 13:09:41 +00:00

heya.. I can cut a release, I'll aim for next weekend. Any particular commit ID I should aim for?

heya.. I can cut a release, I'll aim for next weekend. Any particular commit ID I should aim for?

It should be fine to do whatever master@HEAD is at the time. Thanks!

It should be fine to do whatever master@HEAD is at the time. Thanks!
Owner

Ticket retargeted after milestone closed

Ticket retargeted after milestone closed
meejah modified the milestone from 1.15.0 to soon 2021-03-30 18:40:19 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#3400
No description provided.