Skip to content

Commit

Permalink
chore: Change Release.md
Browse files Browse the repository at this point in the history
  • Loading branch information
s2quake committed Jul 3, 2024
1 parent f87d0fa commit 7b7ae11
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions RELEASE.md
Original file line number Diff line number Diff line change
Expand Up @@ -186,7 +186,7 @@ You also need to prepare the next patch release. Switch to the maintenance
branch (e.g., *1.2-maintenance*), and make sure it is up-to-date.

You need to bump the patch version of the `<VersionPrefix>` field
in the *src/Libplanet/Libplanet.csproj* file. For example, if the version you have
in the *Directory.Build.props* file. For example, if the version you have
just released is *1.2.3*, bump it to *1.2.4* (3 + 1 = 4).

Also the changelog section for the next patch release should be prepared; add
Expand Down Expand Up @@ -236,7 +236,7 @@ git reset --hard upstream/main
~~~~

Since this maintenance branch purposes to prepare the next patch release, e.g.,
*1.2.1*, the `<VersionPrefix>` field of the *src/Libplanet/Libplanet.csproj*
*1.2.1*, the `<VersionPrefix>` field of the *Directory.Build.props*
file also needs to be updated:

~~~~ xml
Expand Down Expand Up @@ -279,7 +279,7 @@ git switch main # Or on Git < 2.23: git checkout main
git fetch upstream && git reset --hard upstream/main
~~~~

Then, in a similar manner, update *src/Libplanet/Libplanet.csproj*'s
Then, in a similar manner, update *Directory.Build.props*'s
`<VersionPrefix>` to *1.3.0*, and add an empty section for *1.3.0* with
the release date undecided to the changelog. Make a commit with a simple
message like <q>Version bump</q>.
Expand Down Expand Up @@ -332,7 +332,7 @@ The checklist to prepare the next release:
5. Switch to the *<var>X</var>.<var>Y</var>-maintenance* branch and
make sure it is up-to-date.
6. Bump `<VersionPrefix>`'s patch version on
*src/Libplanet/Libplanet.csproj*.
*Directory.Build.props*.
(For example, if you have just released *1.2.3*, bump it to *1.2.4*.)
7. Add a new section for the next unreleased version to the changelog,
with the sentence <q>To be released</q> (no release date).
Expand All @@ -344,15 +344,15 @@ The checklist to prepare the next release:

1. Create a new branch named *<var>X</var>.<var>Y</var>-maintenance* and
switch to it.
2. Bump `<VersionPrefix>` on *src/Libplanet/Libplanet.csproj* to
2. Bump `<VersionPrefix>` on *Directory.Build.props* to
*<var>X</var>.<var>Y</var>.1*.
3. Add a new section for the next unreleased version
(*<var>X</var>.<var>Y</var>.1*) to the changelog, with the sentence
<q>To be released</q> (no release date).
4. Commit the changes with a message <q>Version bump</q>.
5. `git push upstream X.Y-maintenance`
6. Switch to the *main* branch.
7. Bump `<VersionPrefix>`'s minor version on *src/Libplanet/Libplanet.csproj*.
7. Bump `<VersionPrefix>`'s minor version on *Directory.Build.props*.
(For example, if you have just released *1.2.0*, bump it to *1.3.0*.)
8. Add a new section for the next unreleased minor version to the
changelog, with the sentence <q>To be released</q> (no release date).
Expand Down

0 comments on commit 7b7ae11

Please sign in to comment.