Author: buildbot
Date: Sun Sep 14 15:37:21 2014
New Revision: 922172
Log:
Staging update by buildbot for maven
Modified:
websites/staging/maven/trunk/content/ (props changed)
websites/staging/maven/trunk/content/developers/release/maven-core-release.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 Sun Sep 14 15:37:21 2014
@@ -1 +1 @@
-1624858
+1624859
Modified:
websites/staging/maven/trunk/content/developers/release/maven-core-release.html
==============================================================================
---
websites/staging/maven/trunk/content/developers/release/maven-core-release.html
(original)
+++
websites/staging/maven/trunk/content/developers/release/maven-core-release.html
Sun Sep 14 15:37:21 2014
@@ -315,8 +315,7 @@ mvn scm-publish:publish-scm</pre></div>
<p>Next, any superceded releases should be removed from the above locations
(after confirming that they exist in
/www/archive.apache.org/dist/maven).</p></div>
<div class="section">
<h4><a name="Proceed_with_Announcement"></a>Proceed with Announcement</h4>
-<p>You can now proceed with the steps outlined after deploying the website on
<a href="./maven-project-release-procedure.html"> Maven Project Common Release
Procedure</a></p>
-<p><b>Note:</b> For Maven core releases, the announcement is additionally sent
to <tt>annou...@apache.org</tt>. This is best done as a separate message to
avoid cross-posting replies.</p></div></div></div>
+<p>You can now proceed with the steps outlined after deploying the website on
<a href="./maven-project-release-procedure.html"> Maven Project Common Release
Procedure</a></p></div></div></div>
</div>
</div>
<div class="clear">
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
