David Cook
2023-08-29 10:06:50 +10:00
parent b826745166
commit 288ec20ddf

@@ -14,7 +14,7 @@
## When do releases happen :steam_locomotive: :train: :train:
Releases follow a set weekly schedule. The release manager in charge will **draft the release on Thursday**, then it will be ready for testers to do their magic and give their approval until the release manager will **publish it on Monday**. Then, we **deploy on Tuesday**.
Releases follow a set weekly schedule. The release manager in charge will **draft the release on Thursday**, then it will be ready for testers to do their magic and give their approval. Then the release manager will usually **publish and deploy** on Tuesday in their local time.
## How to make a release :spiral_notepad: :white_check_mark:
@@ -69,18 +69,13 @@ Keep in mind that any merges done to `master` while the release is in draft won'
**Wait for testers to give the ok** to publish the release. Check the [Testing the release](#testing-the-release) section above for details.
**Announce** in [#global-community](https://openfoodnetwork.slack.com/archives/C59ADD8F2) you just published a new release. Use the template below :point_down: :
```
Hi all, just letting you know that we just released [version number] :tada:.
You can read more about it here: https://github.com/openfoodfoundation/openfoodnetwork/releases/tag/[version number]
```
Ensure the release was announced in [#global-community](https://openfoodnetwork.slack.com/archives/C59ADD8F2) (this should be automatically posted by the GitHub Slack app, after publishing the release).
**Nudge the next person to release**.
## Who has the release power :zap: :muscle:
All Ha-Ri certified/core devs will now do [releases](https://github.com/openfoodfoundation/openfoodnetwork/wiki/Pipeline-development-process#release) on a rotating basis.
All Ha-Ri certified/core devs with server access will now do [releases](https://github.com/openfoodfoundation/openfoodnetwork/wiki/Pipeline-development-process#release) on a rotating basis.
## Deployment