[DOCS] CONTRIBUTING/RELEASE: reusable standard toot

This commit is contained in:
Loïc Dachary 2023-01-20 10:02:10 +01:00
parent e31fff722b
commit d3d074f3d7
No known key found for this signature in database
GPG Key ID: 992D23B392F9E4F2
1 changed files with 10 additions and 2 deletions

View File

@ -19,7 +19,7 @@ From a [Semantic Versioning](https://semver.org/) standpoint, all Forgejo releas
## Release process
When publishing the vX.Y.Z-N release, the following steps must be followed.
When publishing the vX.Y.Z-N release, the following steps must be followed:
### Cherry pick the latest commits from Gitea
@ -27,7 +27,7 @@ The vX.Y/forgejo branch is populated as part of the [rebase on top of Gitea](WOR
* `cherry-pick -x` the commits
* push the vX.Y/forgejo branch including the commits
* verify the tests pass
* verify that the tests pass
### Release Notes
@ -60,6 +60,14 @@ When Forgejo is released, artefacts (packages, binaries, etc.) are first publish
* Verify https://forgejo.org/download/ points to the expected release
* Manually try the instructions to work
### Standard toot
The following toot can be re-used to announce a minor release at `https://floss.social/@forgejo`. For more significant releases it is best to consider a dedicated and non-standard toot.
```
#Forgejo vX.Y.Z-N was just released! This is a minor patch. Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
```
## Release signing keys management
A GPG master key with no expiration date is created and shared with members of the Owners team via encrypted email. A subkey with a one year expiration date is created and stored in the secrets repository, to be used by the CI pipeline. The public master key is stored in the secrets repository and published where relevant.