You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: RELEASE.adoc
+8-22Lines changed: 8 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,18 +20,7 @@ You can manually check at https://github.com/spring-projects/spring-session/mile
20
20
21
21
Update the version number in `gradle.properties` for the release, for example `3.0.0-M1`, `3.0.0-RC1`, `3.0.4`
22
22
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
35
24
36
25
Run the build using
37
26
@@ -40,12 +29,12 @@ Run the build using
40
29
$ ./gradlew check
41
30
----
42
31
43
-
== 6. Push the Release Commit
32
+
== 5. Push the Release Commit
44
33
45
34
Push the commit and GitHub actions will build and deploy the artifacts.
46
35
Wait for the artifact to appear in https://repo1.maven.org/maven2/org/springframework/session/spring-session-core/
47
36
48
-
== 7. Tag the release
37
+
== 6. Tag the release
49
38
50
39
Tag the release and then push the tag
51
40
@@ -54,15 +43,15 @@ git tag 3.0.0-RC1
54
43
git push origin 3.0.0-RC1
55
44
....
56
45
57
-
== 8. Update to Next Development Version
46
+
== 7. Update to Next Development Version
58
47
59
48
Update `gradle.properties` version to next `+SNAPSHOT+` version, update antora.yml and then push
60
49
61
-
== 9. Update version on project pages
50
+
== 8. Update version on project pages
62
51
63
52
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.
Note: Spring Session typically releases only one milestone (M1) and one release candidate (RC1).
104
93
105
-
== 12. Announce the release
94
+
== 11. Announce the release
106
95
107
96
* 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.
0 commit comments