Page History

...

• Create a JIRA ticket for the release tasks and use that ticket number for the commit messages. For example we'll consider MINIFI-458 as our ticket. Also have in mind the release version you are planning for. For example we'll consider '0.5.0'.
• Create the next version in JIRA if necessary so work can continue towards that release.
• Create meaningful release notes for this version if not already created. Enter them here
• Create new branch off 'master' named after the JIRA ticket. Here we'll use a branch off of 'master' with git checkout -b MINIFI-458-RC1

Ensure your Maven settings.xml has been updated as shown below. There are other ways to ensure your PGP key is available for signing as well

...
        <profile>
           <id>signed_release</id>
           <properties>
               <mavenExecutorId>forked-path</mavenExecutorId>
               <gpg.keyname>YOUR GPG KEY ID HERE</gpg.keyname>
               <gpg.passphrase>YOUR GPG PASSPHRASE HERE</gpg.passphrase>
           </properties>
       </profile>
       ...
       <servers>
          <server>
              <id>repository.apache.org</id>
              <username>YOUR USER NAME HERE</username>
              <password>YOUR MAVEN ENCRYPTED PASSWORD HERE</password>
          </server>
       </servers>
       ...

        ...
        <profile>
           <id>signed_release</id>
           <properties>
               <mavenExecutorId>forked-path</mavenExecutorId>
               <gpg.keyname>YOUR GPG KEY ID HERE</gpg.keyname>
               <gpg.passphrase>YOUR GPG PASSPHRASE HERE</gpg.passphrase>
           </properties>
       </profile>
       ...
       <servers>
          <server>
              <id>repository.apache.org</id>
              <username>YOUR USER NAME HERE</username>
              <password>YOUR MAVEN ENCRYPTED PASSWORD HERE</password>
          </server>
       </servers>
       ...

Ensure the the full application build and tests all work by executing mvn -T 2.5C clean install for a parallel build. Once that completes you can startup and test the application by cd nifi-assembly/target then run run "bin/nifiminifi.sh start" in the nifi MiNiFi build. The application should be up and running in a few seconds at http://localhost:8080/nifi

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 -Pcontrib-check should be run as well to help validate. If that doesn't complete cleanly it must be addressed.

...