From ca530aee5597ac6109c3c226b3399e69d025f9f5 Mon Sep 17 00:00:00 2001 From: Marc Wrobel Date: Thu, 21 Jul 2022 00:42:21 +0200 Subject: [PATCH] Update the contribution guide --- CONTRIBUTING.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 771dbec..dc3a94b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -73,8 +73,8 @@ Wait for a bit and you're done. In order to publish a release to Maven Central, you : +- must be a listed collaborator on [`marcwrobel/jbanking`](https://github.com/marcwrobel/jbanking), - must have an account on the [Sonatype Jira issue tracker](https://issues.sonatype.org), -- must be a listed collaboration on [`marcwrobel/jbanking`](https://github.com/marcwrobel/jbanking), - need to declare, in your Maven `settings.xml`, the `oss.sonatype.org` profile and the `sonatype-nexus-staging` server (you can find those declarations in [this sample settings.xml](/.mvn/build-settings.xml)), @@ -89,6 +89,12 @@ mvn release:perform -Prelease If everything went fine, go to [oss.sonatype.org](https://oss.sonatype.org/) and close/release the staging repository. Details are available on the [OSSRH publish guide](https://central.sonatype.org/publish/publish-guide/). +And finally: + +1. declare the release on GitHub (copy the [changelog content](/CHANGELOG.md) in the release notes and create the + related [discussion](https://github.com/marcwrobel/jbanking/discussions)), +2. empty the README for the next release. + ## Continuous Integration Because we are all humans, and to ensure jbanking is stable for everyone, all changes must go through jbanking