Page History

...

1. Update the MiNiFi website to point to the new download(s) by creating a pull request on https://github.com/apache/nifi-site and following the instructions in the README.  Remove older release artifacts from download page (leave the current release and the previous one). For the release just previous to this new one change the links to point to the archive location. See current page as an example of the needed URL changes. In addition to updating the download page as described delete artifacts other than the current/new release from the dist/nifi SVN storage. They are already in the archive location so no need to do anything else.
   
   
2. Update the NiFi Web Page to indicate NEWS of the release as appropriate
   
   
3. Create a proper signed tag of the released codebase based on the RC Tag craeted during the Maven release process.
   
   $ git tag -s rel/minifi-cpp-${MINIFI_VERSION} -m "${JIRA_TICKET} signed release tag for approved release of NiFi MiNiFi C++ ${MINIFI_VERSION}" ${RC_TAG_COMMIT_ID}
   For instructions on setting up to sign your tag see  here .
   
   
4. Push the release tag to the official ASF repository.
   
   $ git push asf rel/minifi-cpp-${MINIFI_VERSION}
   
5. Update the release notes with the final date of the release.
   
   
6. After the release has been complete for 24 hours send the release announcement.
   
   
   • See here for an understanding of why you need to wait 24 hours
   • The announcement should addressed as follows.
     • TO: announce@apache.org, dev@nifi.apache.org
     • REPLY-TO: dev@nifi.apache.org
     • FROM: ${RM_USERID}@apache.org
   • The subject should include [ANNOUNCE] Apache NiFi MiNiFi C++ x.y.z release.
   • The text should on the template included below. +
     
     Hello
     
     The Apache NiFi team would like to announce the release of Apache NiFi MiNiFi C++ ${MINIFI_VERSION}.
     
     

     MiNiFi—a subproject of Apache NiFi—is a complementary data collection approach that supplements the core tenets of NiFi in dataflow management, focusing on the collection of data at the source of its creation.

     Specific goals for the initial thrust of the MiNiFi effort comprise:

     • Small size and low resource consumption
     • Central management of agents
     • Generation of data provenance (full chain of custody of information)
     • Integration with NiFi for follow-on dataflow management
     
     
     Note:  Incorporate highlights about this release to give viewers a succint understanding about why they should care or what is now possible.
     
     More details on Apache NiFi MiNiFi can be found here:
     https://nifi.apache.org/minifi
     
     The release artifacts can be downloaded from here:
     https://nifi.apache.org/minifi/download.html
     
     Maven artifacts have been made available here:
     https://repository.apache.org/content/repositories/releases/org/apache/nifi/
     
     Issues closed/resolved for this list can be found here:
     https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12329373
     
     Release note highlights can be found here:
     https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version${MINIFI_VERSION}
     
     Thank you
     The Apache NiFi team

Release Supporting and Helper Resources

Sample NiFi and MiNiFi Configuration to transmit data from MiNiFi to NiFi via Site to Site

The following archive contains a flow.xml.gz to configure a flow with a known input port UUID to communicate with a configuration for MiNiFI C++ with the included flow.yml. 

minifi-sample-config.tgz

Hashes

• sha1sum: 5b3797924eee1a59421ff216c542cb28c3564bfe

• sha256sum: 9323165a2086053f8d1ad5478e2b7cc97f01fbc38ba133afe77badba1a446833

Signature

Signed with the key at http://people.apache.org/keys/committer/aldrin.asc

minifi-sample-config.tgz.gpg