Repository: nifi-site Updated Branches: refs/heads/master dfc8f5c9d -> 252b45a09
NIFI-1100 Project: http://git-wip-us.apache.org/repos/asf/nifi-site/repo Commit: http://git-wip-us.apache.org/repos/asf/nifi-site/commit/252b45a0 Tree: http://git-wip-us.apache.org/repos/asf/nifi-site/tree/252b45a0 Diff: http://git-wip-us.apache.org/repos/asf/nifi-site/diff/252b45a0 Branch: refs/heads/master Commit: 252b45a099d089148fb14877907423304c7f6275 Parents: dfc8f5c Author: joewitt <joew...@apache.org> Authored: Tue Nov 3 10:52:57 2015 +0000 Committer: joewitt <joew...@apache.org> Committed: Tue Nov 3 10:52:57 2015 +0000 ---------------------------------------------------------------------- src/pages/markdown/release-guide.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/nifi-site/blob/252b45a0/src/pages/markdown/release-guide.md ---------------------------------------------------------------------- diff --git a/src/pages/markdown/release-guide.md b/src/pages/markdown/release-guide.md index ad8b06f..12c7fb6 100644 --- a/src/pages/markdown/release-guide.md +++ b/src/pages/markdown/release-guide.md @@ -261,7 +261,9 @@ Here are the steps of the release once the release is approved: 13. In Jira mark the release version as 'Released' and 'Archived' through 'version' management in the 'administration' console. -14. Wait 24 hours then send release announcement. +14. Create a proper signed tag of the released codebase. If the approved RC tag was 'nifi-0.0.1-RC1' then create a signed release tag of 'nifi-0.0.1'. For instructions on setting up to sign your tag see [here][sign-tag-instructs]. To create a signed release tag enter `git tag -s nifi-0.0.1 -m "Signed release tag for approved release of nifi 0.0.1"` + +15. Wait 24 hours then send release announcement. - See [here][release-announce] for an understanding of why you need to wait 24 hours - Then create an announcement like the one shown below addressed to 'annou...@apache.org, d...@nifi..apache.org' with a reply-to of 'd...@nifi.apache.org'. - The email has to be sent from an apache.org email address and should be by the release manager of the build. @@ -309,3 +311,4 @@ The Apache NiFi team [apache-guide-publish-maven]: http://www.apache.org/dev/publishing-maven-artifacts.html [release-notes]: https://cwiki.apache.org/confluence/display/NIFI/Release+Notes [migration-guide]: https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance +[sign-tag-instructs]: http://gitready.com/advanced/2014/11/02/gpg-sign-releases.html
