Cut an incremental release (2020-09) #3400
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#3400
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
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.
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!
Ticket retargeted after milestone closed