Page History

...

1. Ensure you have completed all the steps in the following sections below:
   1. Appendix A: First Time Release Manager Prep
   2. Appendix B: Configure GPG, Maven, and Git for Signing and Deploying
      
      
2. Create a Jira ticket for the release tasks for this release version. The resulting Jira ticket number is referred to as ${JIRA_TICKET} in this guide. Example:
   

   Jira
   server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key NIFIREG-87

   
   
   
3. If it does not already exist, create the ${VERSION} in Jira from the NiFi Registry Versions management page (requires PMC group access).
   
   
4. Create meaningful release notes for this version if not already created. A good starting point is reviewing the Jira generated release notes from the NiFi Registry Versions management page or this JQL filter: project = NIFIREG and fixVersion = ${VERSION}
   Enter the release notes at the top of the Release Notes page of the NiFi Registry wiki: https://cwiki.apache.org/confluence/display/NIFI/Release+Notes
   It will be necessary to use a placeholder for the release date, which will be updated once the release is finalized.
   
   

5. Create a new branch off ${BRANCH} (typically master) named after the Jira ticket.

   Code Block
   language bash
   git checkout -b ${JIRA_TICKET}-RC${RC} ${BRANCH}

   
   

6. Verify that Maven has sufficient heap space to perform the build tasks. Some plugins and parts of the build consume a surprisingly large amount of space. These settings have been shown to work for Java 8 for NiFi Registry version 0.2.0 and later:

   Code Block
   language bash
   export MAVEN_OPTS="-Xms1024m -Xmx3076m"

   
   

7. Ensure the full application builds and all tests work by executing a full build with tests. The Maven command we use for a full build is in the .travis.yml file at the root of the git repository. At the time of this writing, it is:

   Code Block
   language bash
   mvn clean install -Pcontrib-check,integration-tests,jsUnitTests

   
   

8. Start and test the application from the root source folder. NiFi Registry should be up and running at http://localhost:18080/nifi-registry

   Code Block
   language bash
   cd nifi-registry-assembly/target/nifi-registry-${VERSION}-bin/nifi-registry-${VERSION} ./bin/nifi-registry.sh start

   
   

9. Start and test NiFi pointing to the NiFi Registry by performing basic flow versioning operations.
   
   

10. Evaluate and ensure the appropriate license headers are present on all source files.
    
    

11. Ensure LICENSE and NOTICE files are complete and accurate for both the source and the assembly. (Developers should always be keeping these up to date as they go along adding source and modifying dependencies to keep this burden manageable.)

...