svn commit: r1011735 - in /websites/staging/maven/trunk/content: ./ developers/release/maven-project-release-procedure.html maven-site-1.0-site.jar

[bu...@apache.org]

Author: buildbot
Date: Sat May  6 07:59:31 2017
New Revision: 1011735

Log:
Staging update by buildbot for maven

Modified:
    websites/staging/maven/trunk/content/   (props changed)
    websites/staging/maven/trunk/content/developers/release/maven-project-release-procedure.html
    websites/staging/maven/trunk/content/maven-site-1.0-site.jar

Propchange: websites/staging/maven/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat May  6 07:59:31 2017
@@ -1 +1 @@
-1794127
+1794128

Modified: websites/staging/maven/trunk/content/developers/release/maven-project-release-procedure.html
==============================================================================
--- websites/staging/maven/trunk/content/developers/release/maven-project-release-procedure.html (original)
+++ websites/staging/maven/trunk/content/developers/release/maven-project-release-procedure.html Sat May  6 07:59:31 2017
@@ -185,7 +185,8 @@ Vote open for at least 72 hours.
 [ ] -1
 </pre></div>
 <p>To get the JIRA release notes link, browse to the plugin's JIRA page, select the <i>Road Map</i> link, and use the link to <i>Release Notes</i> that is next to the version being released.</p>
-<p>To get the list of issues left in JIRA, browse to the plugin's JIRA page, and from the <i>Preset Filters</i> on the right, use the link for <i>Outstanding</i> issues.</p></div>
+<p>To get the list of issues left in JIRA, browse to the plugin's JIRA page, and from the <i>Preset Filters</i> on the right, use the link for <i>Outstanding</i> issues.</p>
+<p>The vote is open for at least 72 hours means, that you need to wait at least 72 hours before proceeding. This gives others time to test your release and check that everything is good. If you have received after that not enough +1 votes to reach the quorum, this doesn't mean, the vote failed. It just takes a bit longer.</p></div>
 <div class="section">
 <h3><a name="Check_the_vote_results"></a>Check the vote results</h3>
 <p>Copied from <a class="externalLink" href="https://www.apache.org/foundation/voting.html#ReleaseVotes">Votes on Package Releases</a>.</p>
@@ -214,7 +215,7 @@ I will promote the artifacts to the cent
 <p>If the vote is unsuccessful, the process will need to be restarted. Be sure to drop your staging repository as described in <a class="externalLink" href="https://www.apache.org/dev/publishing-maven-artifacts.html#drop">Dropping a Repo</a>.</p></div>
 <div class="section">
 <h3><a name="Copy_the_source_release_to_the_Apache_Distribution_Area"></a>Copy the source release to the Apache Distribution Area</h3>
-<p>The official Apache release is the 'source-release' bundle. All releases must be copied to <a class="externalLink" href="https://www.apache.org/dist/maven/">the official release area</a>. The release area is maintained with svnsubpub. To deliver a release, you add it to <a class="externalLink" href="https://dist.apache.org/repos/dist/release/maven">the subversion repository for the dist area</a>: add the release, its signature, and corresponding MD5 files. Currently this requires to be in maven-pmc group (see <a class="externalLink" href="https://issues.apache.org/jira/browse/INFRA-5945">https://issues.apache.org/jira/browse/INFRA-5945</a>).</p>
+<p>The official Apache release is the 'source-release' bundle. All releases must be copied to <a class="externalLink" href="https://www.apache.org/dist/maven/">the official release area</a>. The release area is maintained with svnsubpub. To deliver a release, you add it to <a class="externalLink" href="https://dist.apache.org/repos/dist/release/maven">the subversion repository for the dist area</a>: add the release, its signature, and corresponding MD5 files. Currently this requires to be in maven-pmc group (see <a class="externalLink" href="https://issues.apache.org/jira/browse/INFRA-5945">https://issues.apache.org/jira/browse/INFRA-5945</a>). If you are not PMC member, drop a line to <i>private@maven.apache.org</i> and ask them to do this step for you.</p>
 <p>For example:</p>
 <div class="source"><pre class="prettyprint linenums">wagon/wagon-2.2-source-release.zip
 wagon/wagon-2.2-source-release.zip.asc
@@ -231,7 +232,8 @@ wagon/wagon-2.2-source-release.zip.md5</
 <p>As above, deploy the web site if appropriate and update the project site for the new release: use <a href="../website/component-reference-documentation-helper.html">Component Reference Documentation Helper</a> to generate commands or see <a href="../website/deploy-component-reference-documentation.html#Publishing_versioned_component_reference_documentation">Publishing versioned component reference documentation</a> for explanations. Note that not all projects follow these conventions exactly.</p>
 <p>In case there's an overview table with version (e.g. <a href="/plugins/index.html">plugins</a> and <a href="/shared/index.html">shared</a>) update it via <a class="externalLink" href="https://cms.apache.org/">https://cms.apache.org/</a>.</p></li>
 <li>Update the version tracking in JIRA
-<p>In the relevant project, go to Administration, then Versions. Mark the <tt>Y.Z</tt> version as 'released'. Create version <tt>Y.Z+1</tt>, if that hasn't already been done. You may also archive any deprecated releases (milestones or alphas) at this time.</p></li>
+<p>In the relevant project, go to Administration, then Versions. Mark the <tt>Y.Z</tt> version as 'released'. Create version <tt>Y.Z+1</tt>, if that hasn't already been done. You may also archive any deprecated releases (milestones or alphas) at this time.</p>
+<p>Note: Currently this requires to be in the maven-pmc group. So, if you don't see the Administration option in JIRA, kindly ask <i>private@maven.apache.org</i> to do this step for you.</p></li>
 <li>Wait for everything to sync
 <ol style="list-style-type: lower-alpha">
 <li>Sync to <a class="externalLink" href="https://repo.maven.apache.org/maven2/org/apache/maven/">Maven Central</a>

Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.