Author: joewitt Date: Sat Jan 31 04:49:46 2015 New Revision: 1656162 URL: http://svn.apache.org/r1656162 Log: added steps learned from 0.0.1 release
Modified: incubator/nifi/site/trunk/content/development/release-guide.md Modified: incubator/nifi/site/trunk/content/development/release-guide.md URL: http://svn.apache.org/viewvc/incubator/nifi/site/trunk/content/development/release-guide.md?rev=1656162&r1=1656161&r2=1656162&view=diff ============================================================================== --- incubator/nifi/site/trunk/content/development/release-guide.md (original) +++ incubator/nifi/site/trunk/content/development/release-guide.md Sat Jan 31 04:49:46 2015 @@ -148,13 +148,13 @@ This command `mvn install -Pcheck-licens Now its time to have maven prepare the release so execute `mvn release:prepare -Psigned_release -DscmCommentPrefix="NIFI-270-RC1 " -Darguments="-DskipTests"`. Maven will ask: -`What is the release version for "Apache NiFi NAR Plugin"? (org.apache.nifi:nifi) 0.0.1-incubating: :` +`What is the release version for "Apache NiFi"? (org.apache.nifi:nifi) 0.0.1-incubating: :` Just hit enter to accept the default. Maven will then ask: -`What is SCM release tag or label for "Apache NiFi NAR Plugin"? (org.apache.nifi:nifi) nifi-0.0.1-incubating: : ` +`What is SCM release tag or label for "Apache NiFi"? (org.apache.nifi:nifi) nifi-0.0.1-incubating: : ` Enter `nifi-0.0.1-incubating-RC1` or whatever the appropriate release candidate (RC) number is. Maven will then ask: @@ -263,7 +263,7 @@ If so forward the vote to the IPMC. Sen > The vote will be open for 72 hours. > Please download the release candidate and evaluate the necessary items > including checking hashes, signatures, build from source, and test. The > please vote: > -> [ ] +1 Release this package as nar-maven-plugin-0.0.1-incubating +> [ ] +1 Release this package as nifi-0.0.1-incubating > [ ] +0 no opinion > [ ] -1 Do not release this package because because... @@ -291,7 +291,7 @@ Here are the steps of the release once t 2. To produce binary convenience release build the application from the raw source in staging. For each binary convenience artifact: - Generate ascii armored detached signature by running `gpg -a -b nifi-0.0.1-incubating-bin.tar.gz` - Generate md5 hash summary by running `md5sum nifi-0.0.1-incubating-bin.tar.gz | awk '{ printf substr($0,0,32)}' > nifi-0.0.1-incubating-bin.tar.gz.md5` - - Generate sha1 hash summary by running 'sha1sum nifi-0.0.1-incubating-bin.tar.gz | awk '{ printf substr($0,0,40)}' > nifi-0.0.1-incubating-bin.tar.gz.sha1' + - Generate sha1 hash summary by running `sha1sum nifi-0.0.1-incubating-bin.tar.gz | awk '{ printf substr($0,0,40)}' > nifi-0.0.1-incubating-bin.tar.gz.sha1` - Upload the bin, asc, sha1, md5 for each binary convenience build to the same location as the source release 3. In repository.apache.org go to the staging repository and select `release` and follow instructions on the site.