diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2676b1423..353b58b33 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -173,50 +173,4 @@ The *Definition of Done* describes a list of criteria which issues have to meet ### Releasing Metafacture -We use semantic versioning in release numbers `A`.`B`.`C`, i.e. increase `A` when it's a major release breaking backward compatibility; increase `B` when it got new features; increase `C` indicating bug-fixes. - -#### Build and publish to GitHub - -The following commands trigger a release build. - -1. Create a signed tag: - ``` - git tag -s metafacture-core-A.B.C - ``` -1. When prompted, add a sensible commit message. For instance, something like: - ``` - Publish first release of the Metafacture A line - ``` -1. You can now test the build locally by invoking: - ``` - ./gradlew assemble - ``` -1. Finally, push the new tag to GitHub to trigger the actual release build: - ``` - git push --follow-tags metafacture-core-A.B.C - ``` - -#### Publish to Maven Central - -Upload archives to sonatype (where they can be released to Maven Central) - -1. Make sure to have a clean directory (otherwise only a SNAPSHOT will be built): - ``` - git status - ``` -1. You need a `gradle.properties` in the root directory that looks like this: - ``` - signing.gnupg.executable=gpg - signing.gnupg.useLegacyGpg=true - signing.gnupg.homeDir=$e.g."~/.gnupg" - signing.gnupg.keyName=$yourKeyName - signing.gnupg.passphrase=$keysPassphrase - releaseRepositoryUrl=https://oss.sonatype.org/service/local/staging/deploy/maven2/ - releaseRepositoryUser=$yourSonatypeUsername - releaseRepositoryPassword=$yourSonatypePassword - ``` -1. Let the release be built, signed and uploaded: - ``` - ./gradlew publishAllPublicationsToMavenRepository - ``` -1. Finally, go to oss.sonatype.org , check the `Staging Repositories` when it's finished, and release it by clicking `close` +Follow the [wiki's Maintainer-Guidelines](https://github.com/metafacture/metafacture-core/wiki/Maintainer-Guidelines).