ryan-distrust.co/stagex
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

MAINTENANCE: Improve wording about branch creation and targeting

Browse source
This commit is contained in:
ryan 2024-04-01 00:32:55 -04:00
parent 9ee053ab40
commit 01abeb06f3
No known key found for this signature in database
GPG key ID: 8E401478A3FBEF72
1 changed files with 6 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
MAINTENANCE.md
View file

@ -15,13 +15,17 @@ commit.gpgsign true`.
## Release Branches
Release branches take the format `YYYY.MM.release`. A release should include a
PR to staging to introduce a bump to `digests.txt`, then cut into its own
PR to staging to introduce a bump to `digests.txt`, creating the release
branch. Once the branch is created, other users can begin reproducing. The
release engineer should run `make sign` to ensure a signature exists for every
package.
In the Git forge UI, the release pull request should target the `main` branch,
to provide a summary of all changes since the last major code freeze.
Any commits required once the branch is created, but before the release is
published, should flow from the PR branch, to staging, to the release branch.
published, should flow from a PR (if push access is not given) to the release
branch.
Once a release is published, the branch should perform a signed merge commit
into main. Any further pull requests to the branch (which may be published