You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@apex.apache.org by th...@apache.org on 2017/12/02 15:32:43 UTC
[apex-site] branch asf-site updated: from
56f9ea25fb84838af2e3e31e7e7648b743d05300
This is an automated email from the ASF dual-hosted git repository.
thw pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/apex-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 460cef1 from 56f9ea25fb84838af2e3e31e7e7648b743d05300
460cef1 is described below
commit 460cef175a55fbc8486aa8464c12e01a7fcd590c
Author: Apex Dev <de...@apex.apache.org>
AuthorDate: Sat Dec 2 07:31:48 2017 -0800
from 56f9ea25fb84838af2e3e31e7e7648b743d05300
---
content/downloads.html | 8 ++++----
content/release.html | 20 +++++++++++++++-----
2 files changed, 19 insertions(+), 9 deletions(-)
diff --git a/content/downloads.html b/content/downloads.html
index e518b34..34b0519 100644
--- a/content/downloads.html
+++ b/content/downloads.html
@@ -110,7 +110,7 @@
<span class="latest-tag">(latest)</span>
</td>
<td>
- 2017-05-05
+ 2017-05-04
</td>
<td>
<a href="http://www.apache.org/dyn/closer.lua/apex/apache-apex-core-3.6.0/apache-apex-core-3.6.0-source-release.zip">apex-3.6.0-source-release.zip</a><br>
@@ -143,7 +143,7 @@
<span class="latest-tag">(latest)</span>
</td>
<td>
- 2016-12-11
+ 2016-12-10
</td>
<td>
<a href="http://www.apache.org/dyn/closer.lua/apex/apache-apex-core-3.5.0/apache-apex-core-3.5.0-source-release.zip">apex-3.5.0-source-release.zip</a><br>
@@ -192,7 +192,7 @@
<span class="latest-tag">(latest)</span>
</td>
<td>
- 2017-11-12
+ 2017-11-11
</td>
<td>
<a href="http://www.apache.org/dyn/closer.lua/apex/apache-apex-malhar-3.8.0/apache-apex-malhar-3.8.0-source-release.zip">malhar-3.8.0-source-release.zip</a><br>
@@ -225,7 +225,7 @@
<span class="latest-tag">(latest)</span>
</td>
<td>
- 2017-04-01
+ 2017-03-31
</td>
<td>
<a href="http://www.apache.org/dyn/closer.lua/apex/apache-apex-malhar-3.7.0/apache-apex-malhar-3.7.0-source-release.zip">malhar-3.7.0-source-release.zip</a><br>
diff --git a/content/release.html b/content/release.html
index 0393b0c..060d315 100644
--- a/content/release.html
+++ b/content/release.html
@@ -185,6 +185,8 @@ svn import svn-dist https://dist.apache.org/repos/dist/dev/apex/${RNAME}-RC1 -m
<h3 id="javadoc">Javadoc</h3>
<p>Javadoc will be automatically deployed for registered branches. For minor releases, add the new branch to the buildbot configuration:</p>
<p><a href="https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/apex.conf">https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/apex.conf</a></p>
+<p>This essentially means that the file above needs to be edited for the release number in the array of releases. Ensure that you verify the success of the build in the build bot <a href="https://ci.apache.org/builders">url</a>
+Also note that the build bot is a nightly trigger. Wait for atleast the next build trigger to kick in before raising a ticket with the infra team if you see that the javadoc is not appearing as expected.</p>
<h3 id="user-documentation">User Documentation</h3>
<p>The documentation will be generated as static HTML files into the <code>apex-site</code> repository, <a href="https://github.com/apache/apex-site/tree/asf-site/docs">separated by version (X.Y)</a>.</p>
<p><strong>Note</strong> You need Python 2.7+ and <a href="http://www.mkdocs.org/">mkdocs</a> with patch for issue <a href="https://github.com/mkdocs/mkdocs/issues/859">mkdocs #859</a> on top of the currently available version 0.15.3. After installing mkdocs with pip, run the following to obtain this build:</p>
@@ -227,17 +229,19 @@ git push
<a href="https://lists.apache.org/thread.html/2887965dba350e181d06aa02af19d8d47c82eb6f0b47eef8dce14fe8@%3Cdev.apex.apache.org%3E">https://lists.apache.org/thread.html/2887965dba350e181d06aa02af19d8d47c82eb6f0b47eef8dce14fe8@%3Cdev.apex.apache.org%3E</a></p>
<p>Note that the vote result email should have the subject prefixed with <code>[RESULT]</code>.</p>
<p>If the vote is not successful, a new RC needs to be built and new vote called. Once the PMC vote passes, proceed with promoting and announcing the release.</p>
-<h2 id="promote-release">Promote Release</h2>
+<h2 id="promote-release-to-be-done-by-a-pmc-member-">Promote Release (To be done by a PMC member)</h2>
<p>Release Nexus staging repository: <a href="http://central.sonatype.org/pages/releasing-the-deployment.html#close-and-drop-or-release-your-staging-repository">http://central.sonatype.org/pages/releasing-the-deployment.html#close-and-drop-or-release-your-staging-repository</a></p>
<p>Move source release from dist staging to release folder (to be done by PMC member):</p>
<pre><code>rv=3.4.0
RNAME=apache-apex-core-${rv}
svn mv https://dist.apache.org/repos/dist/dev/apex/${RNAME}-RC1 https://dist.apache.org/repos/dist/release/apex/${RNAME} -m "Release ${RNAME}"
-</code></pre><h3 id="jira">JIRA</h3>
-<p>Close release and all associated tickets (use bulk change workflow transition and <strong>turn off notification</strong> at bottom of page to not flood the mailing list).
-Create version number X.Y.Z+1 for next release (to be done by PMC member).</p>
+</code></pre><h3 id="jira-to-be-done-by-a-pmc-member-">JIRA (To be done by a PMC member)</h3>
+<p>The closing of the JIRA item has to be done by a PMC member as the turn off notification for bulk changes in JIRA is an option available only for the PMC members.
+Request a PMC member to close release and all associated tickets (using bulk change workflow transition and <strong>turn off notification</strong> at bottom of page to not flood the mailing list).
+Create version number X.Y.Z+1 for next release (also to be done by PMC member).</p>
<h3 id="git">git</h3>
<p>Create final release tag:</p>
+<p>Note that the value of RC2 in the example below assumes that the second release candidate RC2 is the final release tag. Change this value accordingly.</p>
<pre><code class="lang-bash">rv=3.4.0
git tag -a "v${rv}" -m "Release ${rv}" "v${rv}-RC2"
git push apache "v${rv}"
@@ -254,7 +258,8 @@ published libraries.</p>
<pre><code class="lang-bash">git commit --author "Apex Dev <dev@apex.apache.org>" -am "Preparing for 3.4.1 development"
git push apache
</code></pre>
-<p>Cherry-pick <code>@since</code> tag and change log changes from release tag to <code>master</code>.</p>
+<p>Cherry-pick <code>@since</code> tag and change log changes from release tag to <code>master</code>.
+Push the changes to apache</p>
<h3 id="documentation">Documentation</h3>
<p>If this is a minor or a major release, link the release documentation as latest on the web site. Otherwise it is a patch release and this step can be skipped (documentation is already reflected in the website).</p>
<p>Under the <code>apex-site</code> folder (<code>asf-site</code> branch):</p>
@@ -269,9 +274,14 @@ git push
<h3 id="update-web-site">Update Web Site</h3>
<p>Update the download page to reflect the new release: <a href="https://github.com/apache/apex-site#updating-downloads-page">https://github.com/apache/apex-site#updating-downloads-page</a></p>
<p>Publish the web site, see <a href="https://github.com/apache/apex-site#contributing">apex-site repository</a> for instructions.</p>
+<p>Publishing the site involves running the build.sh script from the master branch and performing a git push from the asf-site branch. The local repo is automatically switched to the asf-site branch when the build.sh script is invoked from the master.</p>
<h2 id="announce-release">Announce Release</h2>
<p>Send the announcement email, example:
<a href="http://mail-archives.apache.org/mod_mbox/www-announce/201605.mbox/%3CCA%2B5xAo1ZYso6azUBJOkpVtJqM%3DAnJFr_RtjKk9_VusBwgYNS8A%40mail.gmail.com%3E">http://mail-archives.apache.org/mod_mbox/www-announce/201605.mbox/%3CCA%2B5xAo1ZYso6azUBJOkpVtJqM%3DAnJFr_RtjKk9_VusBwgYNS8A%40mail.gmail.com%3E</a></p>
+<p>Please include the announce@apache.org as one of the recipients. Also make sure that the email is being sent from the youremail@apache.org email id. Note that the email to announce@apache.org will bounce back if youremail@apache.org email is not configured for the alias address from which you are sending this email.
+The release email must be visible under <a href="https://lists.apache.org/list.html?announce@apache.org">announce mailing list</a></p>
+<h2 id="anouncements-page">Anouncements page</h2>
+<p>Edit the announcements page to publish the feed about the new release by editing the markup file announcements-latest.md under the source tree.</p>
<h2 id="removing-old-releases">Removing old Releases</h2>
<p>As part of publishing new releases, please determine whether old releases should be deleted. See <a href="http://www.apache.org/dev/release.html#when-to-archive">release archiving policy</a> for details why. </p>
<p>With a new patch release, the previous patch release can be removed. For example, once 3.4.1 patch is released, we no longer need to have 3.4.0 on the download page. </p>
--
To stop receiving notification emails like this one, please contact
['"commits@apex.apache.org" <co...@apex.apache.org>'].