Skip to content

Latest commit

 

History

History
70 lines (50 loc) · 2.07 KB

RELEASING.md

File metadata and controls

70 lines (50 loc) · 2.07 KB

Release Guide

The following walks through how we make a release.

Before releasing

Pull main and make sure things build locally fine first.

Sonatype OSSRH Account

The project relies on Sonatype OSSRH (OSS Repository Hosting) for releasing, so you need to have an account and be given the access right to the project.

If you haven't got it yet, follow this guide to acquire it: https://central.sonatype.org/pages/ossrh-guide.html

Once you get the account, set up your default Maven settings ($HOME/.m2/settings.xml) with the Sonatype credentials and GPG passphrase to use for releasing:

    <servers>
        <server>
            <id>oss-sonatype-staging</id>
            <username>myuser</username>
            <password>mypassword</password>
        </server>
        <server>
            <id>oss-sonatype-snapshots</id>
            <username>myuser</username>
            <password>mypassword</password>
        </server>
    </servers>

    <profiles>
        <profile>
            <id>release</id>
            <properties>
                <gpg.passphrase>mypassphrase</gpg.passphrase>
            </properties>
        </profile>
    </profiles>

Releasing

Use the two scripts for releasing a version of the project:

  • release
./bin/release
Use this script to release a version from the snapshot main branch.

Usage:
  release <release_version> <next_snapshot_version> [path to m2 settings file]

So, for example, if you want to release version 1.0.0 then normally all you need to do is run the following command:

./bin/release 1.0.0 1.1-SNAPSHOT

After releasing

Go to GitHub releases page and draft a new release based on the tag you have just released (e.g. camel-catalog-schema-generator-plugin-1.0.0) with release notes, then publish it.

Finally, tweet the new release from @hawtio to let the community know!