CodeCow/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2026-06-27 21:01:32 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs: Add a few notes to release checklist.

Browse Source
This commit is contained in:
Tim Abbott 2021-03-29 00:10:26 -07:00
parent 87c50b1f0a
commit c5ff7daf52
1 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/subsystems/release-checklist.md
View File

@ -9,10 +9,16 @@ preparing a new release.
* Upgrade all Python dependencies in
`requirements` to latest upstream versions so they can burn in (use
`pip list --outdated`).
* Update all the strings on Transifex and
notify translators that they should translate the new strings to get
them in for the next release.
* Create a burn-down list of bugs that need to be fixed before we can
* [Upload strings to
Transifex](../translating/internationalization.html#translation-process)
using `push-translations`. Post a Transifex
[Announcement](https://www.transifex.com/zulip/zulip/announcements/)
notifying translators that we're approaching a release.
* Merge draft updates to the [changelog](../overview/changelog.md)
with changes since the last release. While doing so, take notes on
things that might need follow-up work or documentation before we
can happily advertise them in a release blog post.
* Create a burn-down list of issues that need to be fixed before we can
release, and make sure all of them are being worked on.
* Draft the release blog post (a.k.a. the release notes) in Paper. In
it, list the important changes in the release, from most to least