You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by bu...@apache.org on 2014/03/12 22:33:05 UTC
svn commit: r901335 - in /websites/staging/maven/trunk/content: ./
developers/release/maven-project-release-procedure.html
maven-site-1.0-site.jar
Author: buildbot
Date: Wed Mar 12 21:33:05 2014
New Revision: 901335
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 Wed Mar 12 21:33:05 2014
@@ -1 +1 @@
-1576924
+1576926
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 Wed Mar 12 21:33:05 2014
@@ -13,7 +13,7 @@
</style>
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Jason van Zyl" />
- <meta name="Date-Creation-yyyymmdd" content="20130709" />
+ <meta name="Date-Creation-yyyymmdd" content="20140312" />
<meta name="Date-Revision-yyyymmdd" content="20140312" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -336,7 +336,7 @@ I will promote the artifacts to the cent
wagon/wagon-2.2-source-release.zip.asc
wagon/wagon-2.2-source-release.zip.md5</pre></div>
<p>You should also run 'svn rm' as needed to clear out older releases. As per <a class="externalLink" href="http://www.apache.org/dev/release.html#where-do-releases-go">the policy</a>, only the latest release on a branch should stay in the main dist areas. So long as the previous release is at least a day old, the automatic archiver will have copied it to the archive.</p>
-<p>To check that everything is ok in the dist area, dist-tool-plugin has been written and run once a day to produce <a class="externalLink" href="https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/dist-tool-checksourcerelease.html">"Disttool> Source Release" report</a>.</p></div>
+<p>To check that everything is ok in the dist area, dist-tool-plugin has been written and run once a day to produce <a class="externalLink" href="https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/dist-tool-check-source-release.html">"Disttool> Source Release" report</a>.</p></div>
<div class="section">
<h3>Promote the release<a name="Promote_the_release"></a></h3>
<p>Once the release is deemed fit for public consumption it can be transfered to a production repository where it will be available to all users.</p>
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.