aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNorwin2022-02-27 16:48:09 +0100
committerGitHub2022-02-27 15:48:09 +0000
commitc9da11c6b2c5449b762a4d8458fbbccc5f100b94 (patch)
tree94f3243a5535e4f8a5eaf1d2ea51c646cd8da027
parentaf9da8139a163658f39838c0491c05816d6b4996 (diff)
Add announcement steps to release-howto (#18896)
* add announcements steps to release-howto * Also add homebrew update
-rw-r--r--CONTRIBUTING.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 5a9b9ce7f..4216ee3a1 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -423,6 +423,11 @@ be reviewed by two maintainers and must pass the automatic tests.
* And then push the tag as `git push origin v$vmaj.$vmin.$`. Drone CI will automatically create a release and upload all the compiled binary. (But currently it doesn't add the release notes automatically. Maybe we should fix that.)
* If needed send a frontport PR for the changelog to branch `main` and update the version in `docs/config.yaml` to refer to the new version.
* Send PR to [blog repository](https://gitea.com/gitea/blog) announcing the release.
+* Verify all release assets were correctly published through CI on dl.gitea.io and GitHub releases. Once ACKed:
+ * send a PR to the [homebrew repo](https://gitea.com/gitea/homebrew-gitea) analog to [this PR](https://gitea.com/gitea/homebrew-gitea/commit/1f9a3fe5eb75b64a96a5336665531abcbd0eef0c)
+ * bump the version of https://dl.gitea.io/gitea/version.json
+ * merge the blog post PR
+ * announce the release in discord `#announcements`
## Copyright