GitHub/ergo
3
0
Fork 0
mirror of https://github.com/ergochat/ergo.git synced 2024-11-22 11:59:40 +01:00
Code Issues Projects Releases Wiki Activity

update release branch instructions

Browse Source
This commit is contained in:
Shivaram Lingamneni 2021-02-24 13:21:53 -05:00
parent cbaa6af9bd
commit 640572e151
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
DEVELOPING.md
View File

@ -38,7 +38,8 @@ Develop branches are either used to work out implementation details in preperati
1. Smoke-test a built binary locally 1. Smoke-test a built binary locally
1. Point of no return: `git push origin master --tags` (this publishes the tag; any fixes after this will require a new point release) 1. Point of no return: `git push origin master --tags` (this publishes the tag; any fixes after this will require a new point release)
1. Publish the release on GitHub (Releases -> "Draft a new release"); use the new tag, post the changelog entries, upload the binaries 1. Publish the release on GitHub (Releases -> "Draft a new release"); use the new tag, post the changelog entries, upload the binaries
1. If it's a proper release (i.e. not an alpha/beta), merge the updates into the `stable` branch. 1. Update the `irctest_stable` branch with the new changes (this may be a force push).
1. If it's a production release (as opposed to a release candidate), update the `stable` branch with the new changes. (This may be a force push in the event that stable contained a backport. This is fine because all stable releases and release candidates are tagged.)
1. Make the appropriate announcements: 1. Make the appropriate announcements:
* For a release candidate: * For a release candidate:
1. the channel topic 1. the channel topic