THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Create a JIRA ticket for the release tasks for version ${MINIFI_VERSION}.
_The resulting JIRA ticket number is referred to as ${JIRA_TICKET} in this guide. - Create the next version in JIRA, if it doesn't already exist, so work can continue towards that release. Versions can be managed at https://issues.apache.org/jira/projects/MINIFICPP?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page
- Create meaningful release notes for this version if not already created. Enter them here https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-MiNiFi(C++) on the MiNiFi wiki.
- May be useful to add links to processor documentation so it is easier to diff releases.
- Create a new branch off 'master' ${BRANCH} named after the JIRA ticket.
$ git checkout -b ${JIRA_TICKET}-RC${RC} ${BRANCH} - Verify that you have the needed dependencies to build and run MiNiFi
- Ensure the the full application builds, all tests work, and source passes linting by executing the following:
TODO/DISCUSS: Since we don't have a dependency management framework we will include only base extensions.
mkdir build && cd build && cmake -DPORTABLE=ON .. && make package && make package_source && make test && make linter && make docker - Startup and test the application with from the build folder:
tar xvzf nifi-minifi-cpp-${MINIFI_VERSION}-bin.tar.gz && ./nifi-minifi-cpp-${MINIFI_VERSION}/bin/minifi.sh start - 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.)
...