Author: joewitt
Date: Tue May 5 04:25:59 2015
New Revision: 1677740
URL: http://svn.apache.org/r1677740
Log:
modified profile name to reflect new name 'contrib-check' for NIFI-587
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=1677740&r1=1677739&r2=1677740&view=diff
==============================================================================
--- incubator/nifi/site/trunk/content/development/release-guide.md (original)
+++ incubator/nifi/site/trunk/content/development/release-guide.md Tue May 5
04:25:59 2015
@@ -75,7 +75,7 @@ There are two lists here: one of specifi
-
`https://repository.apache.org/service/local/repositories/orgapachenifi-1011/content/org/apache/nifi/nifi/0.0.1-incubating/nifi-0.0.1-incubating-source-release.zip.asc`
- Need a quick reminder on how to [verify a
signature](http://www.apache.org/dev/release-signing.html#verifying-signature)?
- Do all sources have necessary headers?
- - Unzip the sources file into a directory and execute `mvn install
-Pcheck-licenses`
+ - Unzip the sources file into a directory and execute `mvn install
-Pcontrib-check`
- Are there no unexpected binary files in the release?
- The only thing we'd expect would be potentially test resources files.
- Does the app (if appropriate) execute and function as expected?
@@ -141,7 +141,7 @@ The application should be up and running
Evaluate and ensure the appropriate license headers are present on all source
files. Ensure LICENSE and NOTICE files are complete and accurate.
Developers should always be keeping these up to date as they go along adding
source and modifying dependencies to keep this burden manageable.
-This command `mvn install -Pcheck-licenses` should be run as well to help
validate. If that doesn't complete cleanly it must be addressed.
+This command `mvn install -Pcontrib-check` should be run as well to help
validate. If that doesn't complete cleanly it must be addressed.
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:
