Skip to content

Commit

Permalink
Update RELEASING.md
Browse files Browse the repository at this point in the history
  • Loading branch information
CesarCoelho authored Feb 2, 2023
1 parent 063a9c8 commit 794525c
Showing 1 changed file with 14 additions and 22 deletions.
36 changes: 14 additions & 22 deletions RELEASING.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,8 @@ Prerequisites
* Ask for permissions on the existing ticket [here][sonatype_ticket]

2. Make sure you have a GPG client installed and configured. Check [GNUPG][gnupg]
* Refer to the [GPG Keys][example] guide if you need to set up GPG keys for signing.
* All the information GPG is available [here][gnupg_guide]
* Install the GPG client. In Linux: `sudo apt install gpgv2`
* Refer to the [GPG Keys][example] guide if you need to set up GPG keys for signing. Check also the GPG Guide [here][gnupg_guide]
* Install the GPG client. In Linux: `sudo apt install gnupg`
* Generate a Key Pair with: `gpg --gen-key`
* Distribute the public Key with: `gpg --keyserver keyserver.ubuntu.com --send-keys XXXXXXXXXXXXXXXXXXXXXXXXXXX`

Expand Down Expand Up @@ -44,33 +43,24 @@ Prerequisites
Release to Maven Central
-------------

1. Update the RELEASE_NOTES.md for the impending release and make sure the javadocs generation does not have errors.

1. Do the following tasks:
* Update the RELEASE_NOTES.md for the impending release
* Make sure the javadocs generation does not have any errors: `mvn javadoc:javadoc`
* Make sure the MO Testbeds are passing

2. Update the versions of the pom files. Example, from: 9.0-SNAPSHOT to: 9.0
`git commit -am "Updates the project versions to X.Y"`

3. Compile the projects with sources and javadocs (and enter your GPG Passphrase when prompted):
3. Compile the projects with sources and javadocs (and enter your GPG Passphrase when prompted) and deploy to OSSRH (Maven Central):
```
mvn clean deploy -P release
```

4. Deploy to OSSRH (Maven Central):
```
mvn deploy -P ossrh
```

5. Inspect the staging repository in the Nexus Repository Manager and either trigger a release or drop it:
```
mvn nexus-staging:release
```
If you found a problem, drop it with the command:
```
mvn nexus-staging:drop
```

6. Visit Sonatype Nexus and promote the artifact: https://oss.sonatype.org/
4. Inspect the staging repository in the Nexus Repository Manager [here][oss]
* Release it if everything looks alright
* Or Drop it if there are errors

7. Tag the release in GitHub
5. Tag the release in GitHub


Extra
Expand All @@ -83,3 +73,5 @@ Complete Maven Central publishing guide available [here][sonatype_guide]!
[gnupg]: https://www.gnupg.org/
[example]: https://square.github.io/okio/releasing/#prerequisite-gpg-keys
[gnupg_guide]: https://central.sonatype.org/publish/requirements/gpg/
[oss]: https://oss.sonatype.org/#stagingRepositories

0 comments on commit 794525c

Please sign in to comment.