Versions Compared

Old Version 22

changes.mady.by.user Jared Whiklo

Saved on

compared with

New Version 23

changes.mady.by.user Jared Whiklo

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

The maven release task relies on the tag existing in the repository, make sure there is not a branch with the same name or it will be used instead and cause errors.

...

Code Block
mvn release:perform -DperformRelease -Dgoals=deploy

You will be prompted to enter your GPG passphrase. Ensure you have setup your ~/.m2/settings.xml file with the servers defined on Fedora Release Process

Note
titleYour GPG passphrase may not be masked in terminal.


Expand
titleIf you have more than one GPG key? Click here to expand...

If you have more than one personal key on your GPG keyring, you can specify the correct key by adding

-Darguments=-Dgpg.keyname=<Your Key ID>

to the above mvn command.

Code Block
languagebash
titlefor example
mvn release:perform -DperformRelease -Dgoals=deploy -Darguments=-Dgpg.keyname=<your signing key ID>



...

Docker Release (fcrepo only)

...

 

Expand
titleYou should still have access to your built fcrepo-${CURR}.war file for this.  If you don't click for instructions

Checkout the tagged version of Fedora and build it.

Code Block
git checkout fcrepo-${CURR}
mvn clean install -Pfast-build



This assumes you fcrepo and fcrepo-docker repositories are checked out as siblings.

...

Anchor
push rc to maintenance
push rc to maintenance
Push Release Branch to Maintenance

...

  1. Changing from SNAPSHOT version to release version. Something like [maven-release-plugin] prepare release $REPO-$CURR
  2. Changing from release version to next development version. Something like [maven-release-plugin] prepare for next development iteration

If this appears correct, you can push your release branch on to the maintenance branch.

...