THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Throughout this guide, references must be made to names and values that will vary from release to release. For clarity those variable values have been written like Bash variable references. When a term like "/tmp/src/nifi-${MINIFI_VERSION}" is seen in an instruction or email template it should be replaced with "/tmp/src/nifi-0.7.0" when working the release of "Apache NiFi 0.7.0".
...
Substitutions used in tasks and email templates:
...
| Reference | Example |
|---|
...
| value | Description |
|---|---|
| ${BRANCH} |
...
| 0.7.0- |
...
| SNAPSHOT | the development branch on which the release is based |
...
| ${MINIFI_VERSION} |
...
| 0.7. |
...
| 0 | the version currently in development on the release branch |
...
| ${NEXT_VERSION} |
...
| 0.7.1- |
...
| SNAPSHOT | the future version for development on the release branch |
...
| ${JIRA_TICKET} |
...
| MINIFICPP- |
...
| 2112 | the JIRA ticket created by the release manager for the release tasks |
...
| ${RC} |
...
| 2 | the Release Candidate index start at 1 for the first release candidate |
...
| ${RC_TAG_COMMIT_ID} |
...
| the commit ID of the RC tag created during the Maven release process |
...
| ${RM_USERID} |
...
| johndoe | the Apache account ID of Release Manager |
...
| ${RELEASE_TAG} |
...
| rel/minifi-0.7. |
...
| 0 | the Git repository tag for the source code as released |
...
| ${VOTE_THREAD_URL} |
...
| [0.7.0 vote thread][070-rc2-vote] |
...
| the URL for the Apache Pony Mail archive of the release vote thread |
...
To be practical but avoid confusion with future release details, these example values reflect the previous release NiFi 0.7.0 RC2 release details.
What to validate and how to validate a release
...