-
Notifications
You must be signed in to change notification settings - Fork 35
Release
- Make sure your local repo is up to date
git checkout master
git pull --rebase
On github check the issues and milestones, move any un-fixed issues to the next milestone, close the milestone.
below is an example for non-interactive use, see the release:prepare example and the full documentation for all the details
mvn release:prepare -DautoVersionSubmodules=true -DdevelopmentVersion=4.5.7-SNAPSHOT -DreleaseVersion=4.5.6 -Dtag=v4.5.6
-
-DautoVersionSubmodules=true
: to automatically version all modules in the project -
-DdevelopmentVersion=4.5.7-SNAPSHOT
: This will be the next development version -
-DreleaseVersion=4.5.6
: This is the version number which will be released -
-Dtag=v4.5.6
: The tagname
You can add -l rel-prepare.log
to the command to create a logfile, you can add -DdryRun=true
to see what will happen.
Note you will need an active or cached GIT+SSH connection to the repository to push the tag
Directly after preparing the release you should perform the release; this will build and upload the artifacts into the B3Partners Maven repository.
mvn release:perform
You can add -l rel-perform.log
to the command to create a logfile.
-
Go to github, klick on the releases link. At the top there is a non release tag. Edit the Tag and add some text
-
Publish the release by pressing the button.
-
Mail the mailing list