Spring/spring-data-release
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Reformat release instructions.

Browse Source
This commit is contained in:
Jens Schauder
2021-07-19 12:09:28 +02:00
committed by GitHub
parent 9395fac449
commit 2dbb593676
1 changed files with 32 additions and 47 deletions
Download Patch File Download Diff File Expand all files Collapse all files

79
readme.md
View File

@@ -3,12 +3,14 @@
* Use the command `help` to get a list of all commands in the release tools. * Use the command `help` to get a list of all commands in the release tools.
* After fixing a problem use `workspace cleanup` to cleanup any mess left behind by the previous step. * After fixing a problem use `workspace cleanup` to cleanup any mess left behind by the previous step.
## Setup ## One Time Setup
### Infrastructure requirements ### Infrastructure requirements
- Credentials for `buildmaster` accounts on https://repo.spring.io. - Ensure you have the credentials for `buildmaster` accounts on https://repo.spring.io.
- Credentials for https://oss.sonatype.org (to deploy and promote GA and service releases, need deployment permissions for `org.springframework.data`) in `settings.xml` for server with id `sonatype`. - Ensure yoiu have the credentials for https://oss.sonatype.org (to deploy and promote GA and service releases, need deployment permissions for `org.springframework.data`) in `settings.xml` for server with id `sonatype`.
Both are available in the Spring/Pivotal Last Pass repository.
### Prepare local configuration and credentials ### Prepare local configuration and credentials
@@ -34,53 +36,36 @@ correct Maven, Java, and GPG setup).
See `application-local.template` for details. See `application-local.template` for details.
### Build and execute the release shell
Run `mvn package && java -jar target/spring-data-release-cli.jar`
## The release process ## The release process
### Pre-release checks
Make sure that: | Action | Command |
|--------|---------|
* All work on CVEs potentially contained in the release is done (incl. backports etc.) | Build and execute the release shell | `mvn package && java -jar target/spring-data-release-cli.jar` |
* Upgrade dependencies in Spring Data Build parent pom (mind minor/major version rules) | | *All following commands are run in the release shell* |
* All release tickets are present (`$ tracker releasetickets $trainIteration`) | **Pre-release checks** | |
* Review open tickets for release | Ensure all work on CVEs potentially contained in the release is done (incl. backports etc.) | N.A. |
* Self-assign release tickets (`$ tracker prepare $trainIteration`) | Upgrade dependencies in Spring Data Build parent pom (mind minor/major version rules) | N.A. |
* Announce release preparations to mailing list (https://groups.google.com/forum/#!forum/spring-data-dev) | All release tickets are present | `$ tracker releasetickets $trainIteration` |
| Review open tickets for release | N.A. |
### Release the binaries | Self-assign release tickets | `$ tracker prepare $trainIteration` |
| Announce release preparations to mailing list (https://groups.google.com/forum/#!forum/spring-data-dev) | N.A. |
``` | **Release the binaries** ||
$ release prepare $trainIteration | | `$ release prepare $trainIteration` |
$ release build $trainIteration | Build the artefacts and push them to the apropriate maven repository | `$ release build $trainIteration` |
$ release conclude $trainIteration | |`$ release conclude $trainIteration` |
$ github push $trainIteration | Push the created commits to GitHub |`$ github push $trainIteration` |
$ git backport changelog $trainIteration --target $targets | Backport changes to the backlog to other versions. | `$ git backport changelog $trainIteration --target $targets` |
$ foreach $target -> git push $target | Push the changes of the backlog to GitHub. For each `target` from above do |`$ git push $target` |
``` | **Distribute documentation and static resources from tags** ||
||`$ release distribute $trainIteration`|
### Distribute documentation and static resources from tags | **Post-release tasks** ||
|Close JIRA tickets and GitHub release tickets.|`$ tracker close $trainIteration`|
``` |Create new release versions for upcoming version|`$ tracker create releaseversions $trainIteration.next`|
$ release distribute $trainIteration |Create new release tickets in GitHub |`$ tracker create releasetickets $trainIteration.next`|
``` | Update versions in Sagan. `$targets` is given as comma separated lists of code names, without spaces. E.g. `Moore,Neumann` | `$ sagan update $releasetrains`|
| Create list of docs for release announcements | `$ announcement $trainIteration`|
### Post-release tasks | Announce release (Blog, Twitter) and notify downstream dependency projects as needed. | N.A. |
* Close JIRA tickets and GitHub release tickets.
* Create release tickets for the next train iteration, archive old release versions. Close Jira versions/GitHub milestones.
```
$ tracker close $trainIteration
$ tracker create releaseversions $trainIteration.next
$ tracker create releasetickets $trainIteration.next
```
* Update versions in Sagan with `$ sagan update $releasetrains`.
* Announce release (Blog, Twitter) and notify downstream dependency projects as needed. Dev-tools can assist you with `$ announcement $trainIteration`. Make sure to remove the changelog link to Envers as this module has no changelog.
### Utilities ### Utilities