...
| Note | |||||||
|---|---|---|---|---|---|---|---|
As before, your GPG passphrase may not be masked in terminal.
|
| Note | ||
|---|---|---|
If you get a warning like:
You may need to generate a SSH key, associate it with your Github account and with your local ssh client. More instructions are available on Github |
| 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. |
...
Push Release Branch to Maintenance
The release branch has changes made since code freeze. It also contains the update to the version numbers for future development.
...
Ensure that your commit history matches the release branch's commit history, except for the two additional commits.
- Changing from SNAPSHOT version to release version. Something like [maven-release-plugin] prepare release $REPO-$CURR
- 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.
...