We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
rc
1
1 parent 8abf327 commit 5aa0c7eCopy full SHA for 5aa0c7e
docs/development-process/standard-release-process.md
@@ -27,7 +27,7 @@ process will be described in layer-specific documentation.
27
4. Commit and push the changelog.
28
5. Merge the changes from `develop` into `main`.
29
6. Create and push a tag to `main` that matches the newly bumped version, with
30
- `v` added at the beginning (e.g. `v2.0.1-rc1`).
+ `v` added at the beginning (e.g. `v2.0.1-rc.1`).
31
7. Publish the release on GitHub. The release description should be the same as
32
the release notes for that version. The following artifacts should be
33
uploaded: The image (usually as `wic.gz` and `wic.bmap`), the manifest and
0 commit comments