Skip to content

docs: tell how to push one tag; that rc start with n=0 #3222

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 29, 2025
Merged

docs: tell how to push one tag; that rc start with n=0 #3222

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,18 +28,19 @@ The next step is to create tags to trigger release workflow, **however**
we start by using release candidate tags (`X.Y.Z-rcN`) before tagging the
final release (`X.Y.Z`).

1. Create release candidate tag and push. Increment `N` for each rc.
1. Create release candidate tag and push. The first RC uses `N=0`. Increment
`N` for each RC.
```
git tag X.Y.0-rcN upstream/release/X.Y && git push upstream --tags
git tag X.Y.0-rcN upstream/release/X.Y && git push upstream tag X.Y.0-rcN
```
2. Announce the RC release: see [Announcing Releases]
3. Wait a week for feedback.
* Follow [Patch release with cherry picks] to pull bug fixes into the
release branch.
* Repeat the RC tagging step, incrementing `N`.
4. Finally, tag the final release tag:
```
git tag X.Y.0 upstream/release/X.Y && git push upstream --tags
```shell
git tag X.Y.0 upstream/release/X.Y && git push upstream tag X.Y.0
```

Release automation will create a GitHub release and BCR pull request.
Expand Down