Skip to content

Commit

Permalink
Final-Release: use a more descriptive git tag
Browse files Browse the repository at this point in the history
Use a more descriptive git tag for the release.

The problem with a `24.05`-style tag is, that they *will* land in peoples
pinned sources - and those people will wonder why they never get any
updates.

This changes hopes to make this less prevalent by adding a more descriptive
name for the actual git tag: It tags the branch-off for the new channel
release, but it is *not* the actual channel.
  • Loading branch information
a-kenji committed Sep 14, 2024
1 parent 9e1af00 commit de759f3
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/Final-Release.md
Original file line number Diff line number Diff line change
Expand Up @@ -141,7 +141,7 @@ export NEWVER=23.05
1. Find the commit id and tag the release **on the release branch**:
```bash
git tag --annotate --message="Release $NEWVER" $NEWVER <COMMIT_ID>
git tag --annotate --message="Release $NEWVER" "branch-off-$NEWVER" <COMMIT_ID>
git push upstream $NEWVER
```
Expand Down

0 comments on commit de759f3

Please sign in to comment.