Skip to content

Commit 59fbfd0

Browse files
Update RELEASE.adoc
Closes gh-2298
1 parent d7afde8 commit 59fbfd0

File tree

1 file changed

+8
-22
lines changed

1 file changed

+8
-22
lines changed

RELEASE.adoc

Lines changed: 8 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -20,18 +20,7 @@ You can manually check at https://github.com/spring-projects/spring-session/mile
2020

2121
Update the version number in `gradle.properties` for the release, for example `3.0.0-M1`, `3.0.0-RC1`, `3.0.4`
2222

23-
== 4. Update Antora Version
24-
25-
You will need to update the antora.yml version.
26-
27-
For milestone / release candidate releases you should follow this format:
28-
----
29-
version: '3.0.0-RC1'
30-
prerelease: 'true'
31-
display_version: '3.0.0-RC1'
32-
----
33-
34-
== 5. Build Locally
23+
== 4. Build Locally
3524

3625
Run the build using
3726

@@ -40,12 +29,12 @@ Run the build using
4029
$ ./gradlew check
4130
----
4231

43-
== 6. Push the Release Commit
32+
== 5. Push the Release Commit
4433

4534
Push the commit and GitHub actions will build and deploy the artifacts.
4635
Wait for the artifact to appear in https://repo1.maven.org/maven2/org/springframework/session/spring-session-core/
4736

48-
== 7. Tag the release
37+
== 6. Tag the release
4938

5039
Tag the release and then push the tag
5140

@@ -54,15 +43,15 @@ git tag 3.0.0-RC1
5443
git push origin 3.0.0-RC1
5544
....
5645

57-
== 8. Update to Next Development Version
46+
== 7. Update to Next Development Version
5847

5948
Update `gradle.properties` version to next `+SNAPSHOT+` version, update antora.yml and then push
6049

61-
== 9. Update version on project pages
50+
== 8. Update version on project pages
6251

6352
Update the versions on https://spring.io/projects for Spring Session Core, Spring Session Data Redis, Spring Session JDBC, Spring Session Hazelcast, and Spring Session MongoDB.
6453

65-
== 10. Update Release Notes on GitHub
54+
== 9. Update Release Notes on GitHub
6655

6756
Download
6857
https://github.com/spring-io/github-changelog-generator/releases/latest[the
@@ -91,7 +80,7 @@ cat release-notes | xclip -selection clipboard
9180
https://github.com/spring-projects/spring-session/releases[release on
9281
GitHub], associate it with the tag, and paste the generated notes.
9382

94-
== 11. Close / Create Milestone
83+
== 10. Close / Create Milestone
9584

9685
* In
9786
https://github.com/spring-projects/spring-session/milestones[GitHub
@@ -102,9 +91,6 @@ the new milestone.
10291

10392
Note: Spring Session typically releases only one milestone (M1) and one release candidate (RC1).
10493

105-
== 12. Announce the release
94+
== 11. Announce the release
10695

10796
* Announce via Slack on https://pivotal.slack.com/messages/spring-session[#spring-session], and tag any downstream Spring Session projects (e.g Spring Session for Apache Geode).
108-
109-
Note: Do not post on #spring-release or create a blog post. Those steps happen after the Spring Session BOM is released.
110-

0 commit comments

Comments
 (0)