status-im/status-app
1
0
Fork 0
mirror of https://github.com/status-im/status-app.git synced 2026-08-27 07:01:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(release): add post-release steps

Browse Source
This commit is contained in:
Jonathan Rainville
2026-06-22 15:33:30 -04:00
parent 5a421bd6bd
commit c32b3cdece
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/internal/release-process.md
+8
View File
@@ -67,6 +67,14 @@ This guide is meant to explain the flow and rules of the release process, i.e. t
2. It also lowers the amount of effort needed by devs, as no one needs to cherry-pick
## After the release process
1. A release is considered done once the builds are published to the stores and on Github, plus the release branch is fully rebased on top of master.
2. A new tag **must** be created on the master branch's latest commit with the new version and the `-dev` suffix. eg: `2.39.0-dev` if `2.38.0` was just published.
3. The Status community's control node **should** be updated to the latest version.
4. The Status-Discord bridge **should** be updated to the latest version.
5. Blog posts and News Feed articles **should** be posted.
## Frequently asked questions
### When is a release ready to be cut?