...
Substitutions used in tasks and email templates:
Reference | Example value | Description |
---|
${BRANCH} |
0.7.0-SNAPSHOTmain | the development branch on which the release is based |
${MINIFI_VERSION} | 0. |
710.0 | the version currently in development on the release branch |
${NEXT_VERSION} | 0. |
71-SNAPSHOT0 | the future version for development on the release branch |
${JIRA_TICKET} | MINIFICPP- |
21121234 | the JIRA ticket created by the release manager for the release tasks |
${RC} |
21 | 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/ |
minifi710.0 | the Git repository tag for the source code as released |
${VOTE_THREAD_URL} | [0. |
70700100-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 release details of MiNiFi C++ 0.710.0 RC2 release details.
What to validate and how to validate a release
...