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 (markdown)

Mahmoud Ben Hassine 2023-01-18 10:54:43 +01:00
parent a51f107e10
commit 6052c8fbeb
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
Release-process.md → Release-process-for-v4.md

@ -12,15 +12,15 @@
1.1 Get latest changes from the upstream repository of the branch being released.
1.2 Check if `build.gradle` / `pom.xml` refers to any snapshot/milestone dependencies.
1.2 Check if `build.gradle` refers to any snapshot/milestone dependencies.
1.3 Disable the `Gradle` / `Maven` build plan in Bamboo:
1.3 Disable the `Gradle` build plan in Bamboo:
<img alt="disable-build-plan" src="https://raw.githubusercontent.com/wiki/spring-projects/spring-batch/images/release-process/disable-build-plan.png">
# Part 2: Release to Artifactory
2.1 Run a build of the `Gradle` / `Maven` plan in Bamboo.
2.1 Run a build of the `Gradle` plan in Bamboo.
2.2 Go to `Artifactory build info` and check artifacts:
@ -75,7 +75,7 @@ This staging repository Id is needed for the next step.
### Part 3.2 Release to Maven Central
3.2.1 Go to https://s01.oss.sonatype.org/ and login with `springsource` account (Credentials in LastPass).
3.2.1 Go to https://s01.oss.sonatype.org/ and login with `springsource` account.
3.2.2 In the `Staging Repositories` tab, select the staging repository with the ID from previous step and check its content/activity:
@ -90,7 +90,7 @@ to import jars from it and test them. Otherwise the content will not be visible.
4.1 Update the `current` and `current-SNAPSHOT` symbolic links on the docs server.
4.2 Reactivate the `Gradle` / `Maven` build plan in Bamboo.
4.2 Reactivate the `Gradle` build plan in Bamboo.
4.3 Generate release notes and create a release on Github.
@ -102,7 +102,7 @@ to import jars from it and test them. Otherwise the content will not be visible.
4.7 Post a message in the `#spring-release` slack channel.
4.8 Update `build.gradle` / `pom.xml` with next snapshot versions of Spring Projects.
4.8 Update `build.gradle` with next snapshot versions of Spring Projects.
# Part 5: Rolling Back a release
@ -110,5 +110,5 @@ If anything goes wrong before promoting to Maven Central:
1. Delete version from Artifactory.
2. Delete release branch/tag from git locally and remotely.
3. Revert the version in `gradle.properties` / `pom.xml` and push the change to the upstream repository.
3. Revert the version in `gradle.properties` and push the change to the upstream repository.
4. Restart the release process.