You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-commits@maven.apache.org by bu...@apache.org on 2017/01/16 21:39:31 UTC
svn commit: r1005071 - in /websites/staging/maven/trunk/content: ./
developers/release/maven-project-release-procedure.html
maven-site-1.0-site.jar
Author: buildbot
Date: Mon Jan 16 21:39:31 2017
New Revision: 1005071
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 Mon Jan 16 21:39:31 2017
@@ -1 +1 @@
-1779109
+1779110
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 Mon Jan 16 21:39:31 2017
@@ -228,7 +228,7 @@ wagon/wagon-2.2-source-release.zip.md5</
<li>See <a class="externalLink" href="https://www.apache.org/dev/publishing-maven-artifacts.html#promote">Promoting a Repo</a> for details on promotion.</li>
<li>Deploy the current website
<p>As above, deploy the web site if appropriate and update the project site for the new release. See <a href="../website/deploy-component-reference-documentation.html#Publishing_versioned_component_reference_documentation">Publishing versioned component reference documentation</a> or <a href="../website/component-reference-documentation-helper.html">Component Reference Documentation Helper</a>. Note that not all projects follow these conventions exactly.</p>
-<p>In case there's an overview table with version (e.g. <a class="externalLink" href="http://maven.apache.org/plugins/index.html">plugins</a> and <a class="externalLink" href="https://maven.apache.org/shared/index.html">shared</a> update it via <a class="externalLink" href="https://cms.apache.org/">https://cms.apache.org/</a></p></li>
+<p>In case there's an overview table with version (e.g. <a class="externalLink" href="http://maven.apache.org/plugins/index.html">plugins</a> and <a class="externalLink" href="https://maven.apache.org/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>
<li>Wait for everything to sync
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.