ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2025-04-10 20:30:00 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

different words about asking-about-release

Browse Source
This commit is contained in:
meejah 2020-10-29 18:55:54 -06:00
parent e4ae954ee5
commit 2bcccacc51
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/release-checklist.rst
View File

@ -22,10 +22,11 @@ portion of the release process.
Prepare for the Release
```````````````````````
The `master` branch should always be releasable. However, it is worth
asking on appropriate channels (IRC, the mailing-list, Nuts and Bolts
meetings) whether there are interesting changes that should be
included (or NOT included) etc.
The `master` branch should always be releasable.
It may be worth asking (on IRC or mailing-ist) if anything will be
merged imminently (for example, "I will prepare a release this coming
Tuesday if you want to get anything in").
- Create a ticket for the release in Trac
- Ticket number needed in next section