Page History

...

The purpose of this document is to capture and describe the steps involved in producing an official release of Apache NiFi MiNiFI for both Java and C++ versions. It is written specifically to someone acting in the capacity of a Release Manager (RM).

...

At this point you're on the latest 'master' branch and are able to build the entire application

• 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>
       ...

...