Versions Compared

Old Version 4

changes.mady.by.user Aldrin Piri

Saved on

compared with

New Version 5

changes.mady.by.user Aldrin Piri

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. RM sends a vote request email to the NiFi Developers Mailing List.

  2. RM sends the following helper email to the NiFi Developers Mailing List.

  3. Developers in the community review the release candiate and reply to the vote email with their vote.

  4. After 72 hours if

    • at least 3 binding (PMC members) cast +1 votes, and
    • the positive binding votes out number any negative binding votes
  5. the vote passes and the release candidate is officially released. If the vote does not pass, corrections are made on the release branch and a new release candidate is put forward for a new vote.
  6. RM sends vote result email.

    • TO: dev@nifi.apache.org
    • FROM: ${RM_USERID}@apache.org
    • SUBJECT: [RESULT][VOTE] Release Apache NiFi MiNiFi C++ ${NIFI_VERSION}

      Apache NiFi Community,

      I am pleased to announce that the ${NIFI_VERSION} release of Apache NiFi MiNiFi C++ passes with
        X +1 (binding) votes
        Y -1 (binding) votes
        0 0 votes
        0 -1 votes

      Thanks to all who helped make this release possible.

      Here is the PMC vote thread: ${VOTE_THREAD_URL}

...

  1. Update the MiNiFi website to point to the new download(s). 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/nifiminifi-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/nifiminifi-cpp-${MINIFI_VERSION} rel/nifiminifi-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.

...