Skip to content

Commit 64752de

Browse files
committed
Documentation for release process
1 parent 7b5c5d1 commit 64752de

File tree

1 file changed

+26
-0
lines changed

1 file changed

+26
-0
lines changed

Diff for: PUBLISH.md

+26
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
# Release procedure
2+
3+
First define two environment variables. This will allow you to copy & paste the following commands:
4+
5+
export RELEASE_VERSION="1.0.0"
6+
export DEVELOP_VERSION="1.1.0-SNAPSHOT"
7+
8+
Update the version in `pom.xml` and `README.adoc` to match the version you want to release,
9+
then commit and tag the change.
10+
11+
mvn versions:set -DgenerateBackupPoms=false -DnewVersion=${RELEASE_VERSION}
12+
sed -i "s/\(:version_stable: \).*/\1${RELEASE_VERSION}/g" README.adoc
13+
sed -i "s/\(:version_snapshot: \).*/\1${DEVELOP_VERSION}/g" README.adoc
14+
git commit -am "Preparing ${RELEASE_VERSION} release"
15+
git tag -a -m "v${RELEASE_VERSION}" "v${RELEASE_VERSION}"
16+
17+
Now update the version to match the new 'development version':
18+
19+
mvn versions:set -DgenerateBackupPoms=false -DnewVersion=${DEVELOP_VERSION}
20+
git commit -am "Preparing for next development iteration"
21+
22+
Push the changes and GitLab will build and publish the release.
23+
24+
git push --follow-tags
25+
26+
Log into Sonatype OSSRH interface, close and release the staging repository!

0 commit comments

Comments
 (0)