Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: Joan López de la Franca Beltran <[email protected]>
  • Loading branch information
codebien and joanlopez authored Aug 30, 2024
1 parent 98e6c1e commit d2895d8
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion .github/ISSUE_TEMPLATE/hotfix-release.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ labels: ["release"]

## Release Activities

Note, the assumption is a minor branch release already exists from generated from the latest minor release. It has the name in the form `release-v<major>.<minor>.x`.
Note, the assumption is a minor branch release already exists from the latest minor release. This branch is named in the format `release-v<major>.<minor>.x`.

#### Documentation

Expand Down
4 changes: 2 additions & 2 deletions .github/ISSUE_TEMPLATE/release.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,8 +57,8 @@ labels: ["release"]
- [ ] Merge the release notes PR.
- [ ] Pull locally the previously merged changes.
- [ ] Switch on the release branch then cherry-pick the release notes changes.
- [ ] Directly from the relaese branch, create and push a new tag of the form `v<major>.<minor>.<patch>` using git: `git tag v0.5x.0 -m "v0.5x.0"`.
- [ ] Delete the previous minor's relaese branch. Note, in a major version only the latest minor is actively maintained.
- [ ] Directly from the release branch, create and push a new tag of the form `v<major>.<minor>.<patch>` using git: `git tag v0.5x.0 -m "v0.5x.0"`.
- [ ] Delete the previous minor's release branch. Note, in a major version only the latest minor is actively maintained.

#### Announcements

Expand Down

0 comments on commit d2895d8

Please sign in to comment.