Skip to content
Permalink
Browse files
Update release howto to accomodate discrepancies in release managemen…
…t process...
  • Loading branch information
lewismc committed Mar 4, 2019
1 parent c83f413 commit 483ca72e2145a0766ec3af5719406b9fbdf226fa
Showing 1 changed file with 29 additions and 63 deletions.
@@ -218,57 +218,39 @@ gpg: Signature made ...</source>
</ol>
</li>

<li>Add the distribution artifacts to the build area (the <a href="https://svn.apache.org/repos/asf/any23/committers/scripts/grab-binaries.sh">grab-binaries.sh</a>
script is versioned under the committer space of Any23 SVN).
<source>ssh asf-id@people.apache.org
cd /x1/builds/any23

sh grab-binaries.sh REPO_ID ANY23_VERSION CRAWLER_VERSION HTML_SCRAPER_VERSION OFFICE_SCRAPER_VERSION</source>
<li>Add the distribution artifacts to the dev staging area at <a href="https://dist.apache.org/repos/dist/dev/any23/">https://dist.apache.org/repos/dist/dev/any23/</a> ensuring that you provide SHA512 and ASC signatures all relevant artifacts.
</li>
</ol>
</li>

<li>
This step will create the staging site: From the directory where you have launched <tt>release:perform</tt> execute:
<source>cd target/checkout
svn checkout https://svn.apache.org/repos/asf/any23/site/ staging-site
mvn -P site site-deploy -Dsite.deploymentBaseUrl=file:///&lt;absolute path to/&lt;staging-site/version&gt;&gt;
cd staging-site
svn add &lt;version&gt;
svn commit -m "staging site for release"</source>
</li>
</ol>
</subsection>

<subsection name="Vote the Release">
<ol>
<li>Create a <code>VOTE</code> email thread on <a href="mailto:any23-dev@apache.org">any23-dev</a>
<li>Create a <code>VOTE</code> email thread on <a href="mailto:dev@any23.apache.org">dev@any23.apache.org</a> and <a href="mailto:user@any23.apache.org">user@any23.apache.org</a>
to record votes as replies, e.g.:
<pre><![CDATA[To: "Apache Any23 Developers List" <any23-dev@apache.org>
<pre><![CDATA[To: "Apache Any23 Developers List" <dev@any23.apache.org>, "Apache Any23 Users List" <user@any23.apache.org>
Subject: [VOTE] Release Apache Any23 X.Y
Hi,
Please VOTE on the release candidate for Apache Any23 ${latestStableRelease}
We solved N issues:
http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312323&styleName=Html&version=X.Y
There are still a couple of issues left in JIRA:
http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12312323&status=1
Git source tag (r9999999):
https://git-wip-us.apache.org/repos/asf/any23.git ...
https://gitbox.apache.org/repos/asf/any23.git ...
Staging repo:
https://repository.apache.org/content/repositories/orgapacheany23-[YOUR REPOSITORY ID]/
Staging binaries:
http://people.apache.org/builds/any23/
Staging site:
http://any23.apache.org/X.Y/
https://dist.apache.org/repos/dist/dev/any23/${latestStableRelease}
PGP release keys (signed using ABCDEFG):
http://any23.apache.org/dist/KEYS
https://dist.apache.org/repos/dist/release/any23/KEYS
Vote will be open for 72 hours.
@@ -277,25 +259,8 @@ Vote will be open for 72 hours.
[ ] -1, nope, because... (and please explain why)]]></pre>
</li>

<li>Create a <code>DISCUSS</code> email thread on <code>any23-dev@</code> for any vote questions, e.g.:
<pre><![CDATA[To: "Apache Any23 Developers List" <any23-dev@apache.org>
Subject: [DISCUSS] Apache Any23 X.Y
Discussion thread for vote on &lt;version&gt; release candidate, with SVN source tag (r9999999).
For more information on the release process, check out http://www.apache.org/dev/release.html
Some of the things to check before voting are:
- does "mvn rat:check" pass on the source
- can you build the contents of source-release.zip and Git tag
- do all of the staged jars/zips contain the required LICENSE and NOTICE files
- are all of the staged jars signed and the signature verifiable
- is the signing key in the project's KEYS file and on a public server (i.e. http://www.apache.org/dist/any23/)]]>
</pre>
</li>

<li>Perform a review of the release and cast your vote. For more details on Apache releases see
<a href="http://www.apache.org/dev/release.html">http://www.apache.org/dev/release.html</a>.</li>
<a href="http://www.apache.org/legal/release-policy.html">http://www.apache.org/legal/release-policy.html</a>.</li>

<li>A <code>-1</code> vote does not necessarily mean that the vote must be redone, however it is usually a
good idea to rollback the release if a <code>-1</code> vote is received
@@ -304,8 +269,8 @@ Some of the things to check before voting are:
<li>After the vote has been open for at least 72 hours, has at least three +1 PMC votes and no -1 votes, then
post the results to the vote thread, replying to the initial email prepending <code>[RESULT]</code> to the
original subject and include a list of every binding <code>+1</code>, <code>0</code> and <code>-1</code> vote.
<pre><![CDATA[To: "Apache Any23 Developers List" <any23-dev@apache.org>
CC: "Apache Any23 PMC List" <any23-private@apache.org>
<pre><![CDATA[To: "Apache Any23 Developers List" <dev@any23.apache.org>
CC: "Apache Any23 PMC List" <private@any23.apache.org>
Subject: [RESULT] [VOTE] Release Apache Any23 X.Y
Hi,
@@ -340,13 +305,7 @@ I will promote the artifacts to the central repo.]]></pre>
</ol>
</li>

<li>Add the distribution artifacts to the distribution area
<source>ssh asf-id@people.apache.org
cd /x1/www/www.apache.org/dist/any23/

mv /x1/builds/any23/sources/* sources/
mv /x1/builds/any23/binaries/* binaries/</source>
</li>
<li>Move the distribution artifacts from the dev staging area at <a href="https://dist.apache.org/repos/dist/dev/any23/">https://dist.apache.org/repos/dist/dev/any23/</a> to the release area at <a href="https://dist.apache.org/repos/dist/release/any23/">https://dist.apache.org/repos/dist/release/any23/</a> ensuring that you provide SHA512 and ASC signatures all relevant artifacts.</li>

<li>Update the
<a href="https://issues.apache.org/jira/plugins/servlet/project-config/ANY23/versions">JIRA versions</a>
@@ -357,28 +316,35 @@ mv /x1/builds/any23/binaries/* binaries/</source>

<subsection name="Announce the Release">
<p>Make an announcement about the release on the
<a href="mailto:any23-user@apache.org">any23-user</a>,
<a href="mailto:any23-dev@apache.org">any23-dev</a>, and
<a href="mailto:user@any23.apache.org">any23-user</a>,
<a href="mailto:dev@any23.apache.org">any23-dev</a>,
<a href="https://groups.google.com/d/forum/web-data-commons">Web Data Commons - Google Group</a>,
maybe some other relevant W3C and/or OGC groups, and
<a href="mailto:announce@apache.org">announce@apache.org</a> lists as per
<a href="http://www.apache.org/foundation/mailinglists.html#foundation-announce]">the Apache Announcement Mailing Lists page</a>
<a href="http://www.apache.org/foundation/mailinglists.html#foundation-announce">the Apache Announcement Mailing Lists page</a>
</p>

<pre><![CDATA[From: YOUR_APACHE_USERNAME@apache.org
To: "ASF Announcements" <announce@apache.org>, "Apache Any23 Users List" <any23-user@apache.org>
CC: "Apache Any23 Developers List" <any23-dev@apache.org>
To: "ASF Announcements" <announce@apache.org>, "Apache Any23 Users List" <user@any23.apache.org>
CC: "Apache Any23 Developers List" <dev@any23.apache.org>
Subject: [ANNOUNCE] Apache Any23 X.Y
The Apache Any23 Team is pleased to announce the release of Apache Any23 X.Y.
The Apache Any23 Team is pleased to announce the release of Apache Any23 ${latestStableRelease}.
Anything To Triples (any23) is a library, a web service and a command line tool that
Apache Anything To Triples (Any23) is a library, a web service and a command line tool that
extracts structured data in RDF format from a variety of Web documents.
Release Notes:
Release Notes: https://github.com/apache/any23/blob/any23-${latestStableRelease}/RELEASE-NOTES.txt
Download: http://any23.apache.org/download.html
Maven Artifacts: https://s.apache.org/mwOE
(put JIRA release notes here)
DOAP: https://github.com/apache/any23-committers/blob/master/doap_Any23.rdf
Have Fun,
(committer name), on behalf of the Apache Any23 PMC]]></pre>
(Lewis), on behalf of the Apache Any23 PMC
N.B. The release artifacts can take a bit of time to reach the distribution servers, please be patient.]]></pre>
</subsection>
</section>

0 comments on commit 483ca72

Please sign in to comment.