...
If any online resources have been modified or added to during the release, these must be updated.
Release Day
...
Determine which modules will be released.
...
| Code Block |
|---|
git clone git@github.com:$ORG/$REPO.git
cd $REPO
git checkout rc-$CURR
mvn release:clean
# if that fails, do "git revert HEAD" and retry
# if it can't find an old fcrepo4 snapshot, build an old version to populate it locally
|
If release:clean fails, you may need to revert the RC commit with git revert HEAD. If the parent snapshot is not available, build an old version of fcrepo4 to populate it locally.
| Code Block |
|---|
mvn release:prepare -DreleaseVersion=$CURR -DdevelopmentVersion=$NEXT -DautoVersionSubmodules=true -DpushChanges=false |
Resolve dependencies and set main versions to $CURR and dev versions to $NEXT
| Note |
|---|
Your GPG passphrase will not be masked in terminal. |
| Code Block |
|---|
# resolve dependencies and set main versions to $CURR and dev versions to $NEXT
# n.b., GPG passphrase will not be masked in terminal
rm -rf ~/.m2/repository/org/fcrepo
git checkout $REPO-$CURR # detached head state
mvn clean install
|
...
| Code Block |
|---|
mvn release:perform -DperformRelease -Dgoals=deploy
# as |
| Note |
|---|
As before, your GPG passphrase will not be masked in terminal. |
| Warning | ||
|---|---|---|
| ||
The following steps, once completed are final. They cannot be undone, revoked or altered. Only proceed if you've completed all the above steps and are absolutely certain the release is ready for publication. |
...