You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by al...@apache.org on 2017/06/02 19:02:31 UTC
svn commit: r1797420 - /nifi/site/trunk/release-guide.html
Author: aldrin
Date: Fri Jun 2 19:02:31 2017
New Revision: 1797420
URL: http://svn.apache.org/viewvc?rev=1797420&view=rev
Log:
NIFI-3864 Providing information in the release guide as to how to handle Docker versioning.
Modified:
nifi/site/trunk/release-guide.html
Modified: nifi/site/trunk/release-guide.html
URL: http://svn.apache.org/viewvc/nifi/site/trunk/release-guide.html?rev=1797420&r1=1797419&r2=1797420&view=diff
==============================================================================
--- nifi/site/trunk/release-guide.html (original)
+++ nifi/site/trunk/release-guide.html Fri Jun 2 19:02:31 2017
@@ -516,6 +516,12 @@ Here is the PMC vote thread: ${VOTE_THRE
<li><p>Merge the release branch into master.</p>
<pre><code> $ git push asf NIFI-${JIRA_TICKET}</code></pre>
</li>
+<li><p>Update Docker version information to point to the next release. For instance, if the next version applied by Maven is 1.3.0-SNAPSHOT, these values should be updated to 1.3.0. This currently consists of two files:</p>
+<ul>
+<li><a href="https://github.com/apache/nifi/blob/master/nifi-docker/dockerhub/Dockerfile#L24">nifi-docker/dockerhub/Dockerfile, Line 24</a>, and</li>
+<li><a href="https://github.com/apache/nifi/blob/master/nifi-docker/dockerhub/DockerImage.txt#L16">nifi-docker/dockerhub/DockerImage.txt, Line 16</a>.</li>
+</ul>
+</li>
<li><p>Update the NiFi 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
@@ -535,7 +541,9 @@ in the archive location so no need to do
<li>wget <a href="http://localhost:8080/nifi-docs/documentation">http://localhost:8080/nifi-docs/documentation</a> and svn commit to <a href="https://svn.apache.org/repos/asf/nifi/site/trunk/docs/nifi-docs/index.html">https://svn.apache.org/repos/asf/nifi/site/trunk/docs/nifi-docs/index.html</a></li>
</ol>
</li>
-<li><p>In Jira mark the release version as 'Released' and 'Archived' through 'version' management in the 'administration' console.</p>
+<li><p>In JIRA mark the release version as 'Released' and 'Archived' through 'version' management in the 'administration' console.</p>
+</li>
+<li><p>Ensure the release artifacts are successfully mirrored to the archive, specifically <a href="https://archive.apache.org/dist/nifi/${NIFI_VERSION}/nifi-${NIFI_VERSION}-bin.tar.gz">https://archive.apache.org/dist/nifi/${NIFI_VERSION}/nifi-${NIFI_VERSION}-bin.tar.gz</a>. This convenience binary file is the basis for our <a href="https://hub.docker.com/r/apache/nifi">Docker build</a> and is needed in place before the released tag is pushed to the repository. If there were any issues with the above listed file not being available, it may be necessary to reach out to the ASF Infra team to adjust file size limits to accommodate larger artifacts.</p>
</li>
<li><p>Create a proper signed tag of the released codebase based on the RC Tag created during the Maven release process.</p>
<pre><code>$ git tag -s rel/nifi-${NIFI_VERSION} -m "${JIRA_TICKET} signed release tag for approved release of NiFi ${NIFI_VERSION}" ${RC_TAG_COMMIT_ID}</code></pre>
@@ -544,6 +552,8 @@ in the archive location so no need to do
<li><p>Push the release tag to the official ASF repository.</p>
<pre><code>$ git push asf rel/nifi-${NIFI_VERSION} rel/nifi-${NIFI_VERSION}</code></pre>
</li>
+<li><p>Verify that the Docker build began at the <a href="https://hub.docker.com/r/apache/nifi/builds/">Build Status</a> page. If the build does not take place soon after the release tag was pushed, it may be necessary to contact ASF Infra to ask for assistance and the job to be triggered again.</p>
+</li>
<li><p>Update the release notes with the final date of the release.</p>
</li>
<li><p>After the release has been complete for 24 hours send the release announcement.</p>