foster/forgejo-docs
0
0
Fork 0
mirror of https://codeberg.org/forgejo/docs.git synced 2024-11-21 17:36:59 -05:00
Code Issues Activity

developer: release: cut the documentation branch

Browse source 
- 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
This commit is contained in:
Earl Warren 2024-04-21 09:20:48 +02:00 committed by Earl Warren
parent 5471e62e60
commit 5acda1e0b2
2 changed files with 6 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
.forgejo/workflows/push.yml
View file

@ -4,10 +4,7 @@ on:
push:
branches:
- 'next'
- 'v7.0'
- 'v1.21'
- 'v1.20'
- 'v1.19'
- 'v*'
jobs:
publish:

5
docs/developer/RELEASE.md
View file

@ -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