From 5acda1e0b2f019e3a0ea7c9dc74987bf05956e41 Mon Sep 17 00:00:00 2001 From: Earl Warren Date: Sun, 21 Apr 2024 09:20:48 +0200 Subject: [PATCH] developer: release: cut the documentation branch - add a checklist to the release instructions - use a pattern for push instead of an explicit list of branches it was previously advisable to avoid conflicts when there was no automated backports but it is no longer necessary --- .forgejo/workflows/push.yml | 5 +---- docs/developer/RELEASE.md | 5 +++++ 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/.forgejo/workflows/push.yml b/.forgejo/workflows/push.yml index 25a0c107..d2d80784 100644 --- a/.forgejo/workflows/push.yml +++ b/.forgejo/workflows/push.yml @@ -4,10 +4,7 @@ on: push: branches: - 'next' - - 'v7.0' - - 'v1.21' - - 'v1.20' - - 'v1.19' + - 'v*' jobs: publish: diff --git a/docs/developer/RELEASE.md b/docs/developer/RELEASE.md index 305ae8e2..972ca50f 100644 --- a/docs/developer/RELEASE.md +++ b/docs/developer/RELEASE.md @@ -81,6 +81,11 @@ When a new `vX.Y.Z` release is ready to enter the release candidate stages: - Add add a `vX.Y/forgejo` branch protection rule https://codeberg.org/forgejo/forgejo/settings/branches - Trigger a mirror workflow in https://codeberg.org/forgejo/forgejo and verify the `X.Y-test` and `(X+1).0-test` releases are published in https://codeberg.org/forgejo-experimental - Update end-to-end to [know about the new release](https://code.forgejo.org/forgejo/end-to-end/pulls/139). It must be done after the first `(X+1).0-test` release is available in experimental otherwise it will fail to find it and will block the automated release process in the forgejo-integration repository +- Documentation + - In [the documentation](https://codeberg.org/forgejo/docs) + - Create the `vX.Y` branche from next + - Create the `backport/vX.Y` label + - In [the website](https://codeberg.org/forgejo/website) add a submodule similar to [this commit](https://codeberg.org/forgejo/website/commit/3f1e62be22f96d048309157e8779cbfcf204eb90) ### Release Notes