Spring/spring-batch
Spring/spring-batch
1
0
Fork 0
mirror of https://github.com/spring-projects/spring-batch.git synced 2024-07-14 23:56:54 +08:00
Code Issues Packages Projects Releases Wiki Activity

Updated Release process for v5 (markdown)

Mahmoud Ben Hassine 2023-12-13 14:35:33 +01:00
parent 6fd90dfba9
commit 41f65550f6
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Release-process-for-v5.md

@ -24,7 +24,7 @@
3.2 Run the "Maven Central Release" workflow **from the branch to release** ❗ and provide the version to release. This will download the artifacts from the Artifactory staging repository, sign them with GPG and upload them to Maven Central.
# Part 4: Tag the release
### Part 4: Tag the release
None of the previous Github Actions changes the version in the code and pushes the changes to the upstream repository. The version change is done manually **on purpose**. At this point, the release should have been staged, tested and promoted to Maven Central. It is now safe to change the version in the code and push it to the upstream repository. From the root directory of the project, run the following commands (change the version number accordingly):
@ -40,7 +40,7 @@ $git push upstream v5.0.5
NB: The "v" prefix in the tag name is important, see https://github.com/spring-projects/spring-batch/issues/4183.
# Part 5: Update the documentation
### Part 5: Update the documentation
1. Go to Github Actions: https://github.com/spring-projects/spring-batch/actions.
2. Run the "Documentation Upload" workflow **from the branch to release** ❗and provide the version to release. This will generate a distribution of the documentation (java docs and XSDs) and upload it to the documentation server where needed.
@ -58,7 +58,7 @@ Check uploaded jars in http://repo.spring.io/libs-milestone-local/org/springfram
❗ Heads-up: The "Artifactory Milestone Release" workflow is designed to be idempotent (it has no git side effects). If something is wrong with the milestone release, the same workflow can be re-run with the same version and a new milestone will override the corrupted one on the milestone repository. ❗
# Part 3: Tag the release
### Part 3: Tag the release
None of the previous Github Actions changes the version in the code and pushes the changes to the upstream repository. The version change is done manually **on purpose**. At this point, the release should have been staged, tested and promoted to Artifactory. It is now safe to change the version in the code and push it to the upstream repository. From the root directory of the project, run the following commands (change the version number accordingly):
@ -74,7 +74,7 @@ $git push upstream v5.2.0-M1
NB: The "v" prefix in the tag name is important, see https://github.com/spring-projects/spring-batch/issues/4183.
# Part 4: Update the documentation
### Part 4: Update the documentation
1. Go to Github Actions: https://github.com/spring-projects/spring-batch/actions.
2. Run the "Documentation Upload" workflow from the `main` branch and provide the milestone version to release. This will generate a distribution of the documentation (java docs and XSDs) and upload it to the documentation server where needed.