From 487db465b1cd0334552b7f228d36d477722a1d31 Mon Sep 17 00:00:00 2001 From: Norwin Date: Fri, 25 Feb 2022 15:13:58 +0100 Subject: [PATCH 1/2] add announcements steps to release-howto --- CONTRIBUTING.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5a9b9ce7fc62..25889629309b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -423,6 +423,10 @@ 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: + * merge the blog post PR + * bump the version of https://dl.gitea.io/gitea/version.json + * announce the release in discord #announcements ## Copyright From 1f60c457e0992d2f3ba2492102ce35a8d9078498 Mon Sep 17 00:00:00 2001 From: Norwin Date: Fri, 25 Feb 2022 15:17:55 +0100 Subject: [PATCH 2/2] Also add homebrew update --- CONTRIBUTING.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 25889629309b..4216ee3a13a1 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -423,10 +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: - * merge the blog post PR +* 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 - * announce the release in discord #announcements + * merge the blog post PR + * announce the release in discord `#announcements` ## Copyright