svn commit: r828592 - in /websites/staging/maventest/trunk/content: ./ developers/release/maven-plugin-release.html

[bu...@apache.org]

Author: buildbot
Date: Fri Aug 10 21:53:04 2012
New Revision: 828592

Log:
Staging update by buildbot for maventest

Modified:
    websites/staging/maventest/trunk/content/   (props changed)
    websites/staging/maventest/trunk/content/developers/release/maven-plugin-release.html

Propchange: websites/staging/maventest/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Aug 10 21:53:04 2012
@@ -1 +1 @@
-1371826
+1371827

Modified: websites/staging/maventest/trunk/content/developers/release/maven-plugin-release.html
==============================================================================
--- websites/staging/maventest/trunk/content/developers/release/maven-plugin-release.html (original)
+++ websites/staging/maventest/trunk/content/developers/release/maven-plugin-release.html Fri Aug 10 21:53:04 2012
@@ -227,7 +227,7 @@ mvn -Preporting site site:stage scm-publ
     -Dscmpublish.pubScmUrl=scm:svn:https://svn.apache.org/repos/infra/websites/production/maventest/content/plugins/maven-XXX-plugin-latest
 
 svn cp https://svn.apache.org/repos/infra/websites/production/maventest/content/plugins/maven-XXX-plugin-latest \
-       https://svn.apache.org/repos/infra/websites/production/maventest/content/plugins/maven-XXX-plugin-Y.Z</pre></div><p><b>Note:</b> You should verify the deployment of the site on the Maven website (you need to wait <a class="externalLink" href="http://www.apache.org/dev/cms.html#svnpubsub">snvpubsub</a>), which should be a matter of seconds.</p><div class="source"><pre>http://maven.apache.org/plugins/maven-XXX-plugin-Y.Z/</pre></div></li><li>declare the <tt>plugins/maven-XXX-plugin-Y.Z</tt> directory in <a href="/extpaths.txt">extpaths.txt</a>, locally or <a class="externalLink" href="https://cms.apache.org/redirect?uri=http://maventest.apache.org/extpaths.txt&amp;action=edit">with the CMS</a>.</li></ol></div><div class="section"><h3>Publishing the release website<a name="Publishing_the_release_website"></a></h3><p>After the release has passed, the site needs to be updated to point to the new release: edit the content/filtered-resources/.htaccess file (locally or <a cla
 ss="externalLink" href="https://cms.apache.org/redirect?uri=http://maventest.apache.org/filtered-resources/.htaccess&amp;action=edit">with the CMS</a>) to update rewrite rule</p><div class="source"><pre>RewriteRule ^plugins/maven-XXX-plugin/(.*)$ /plugins/maven-XXX-plugin-Y.Z/$1 [L]</pre></div></div><div class="section"><h3>Updating the Maven site<a name="Updating_the_Maven_site"></a></h3><p>Use the CMS to update <a href="/plugins/">the plugins page</a>, made easy with the CMS bookmarklet.</p></div><div class="section"><h3>idea to be developped if sufficient people is interested<a name="idea_to_be_developped_if_sufficient_people_is_interested"></a></h3><p>Instead of doing command line svn and extpaths.txt + .htaccess edits, the staging/release operations could be automated as web ui like following:</p><ul><li>http://cms.apache.org/maventest/release/plugins/maven-xxx-plugin-X.Y could display a page proposing to <b>stage the release documentation</b> (doing svn command and .ht
 access edit)</li><li>next time this page is displayed, with the content already available in svn, the page could propose 2 different actions: <b>drop the staged documentation</b> (with extpaths.txt removal) or <b>publish the release website</b>.</li></ul></div></div>
+       https://svn.apache.org/repos/infra/websites/production/maventest/content/plugins/maven-XXX-plugin-Y.Z</pre></div><p><b>Note:</b> You should verify the deployment of the site on the Maven website (you need to wait <a class="externalLink" href="http://www.apache.org/dev/cms.html#svnpubsub">snvpubsub</a>), which should be a matter of seconds.</p><div class="source"><pre>http://maven.apache.org/plugins/maven-XXX-plugin-Y.Z/</pre></div></li><li>declare the <tt>plugins/maven-XXX-plugin-Y.Z</tt> directory in <a href="/extpaths.txt">extpaths.txt</a>, locally or <a class="externalLink" href="https://cms.apache.org/redirect?uri=http://maventest.apache.org/extpaths.txt&amp;action=edit">with the CMS</a>.</li></ol></div><div class="section"><h3>Publishing the release website<a name="Publishing_the_release_website"></a></h3><p>After the release has passed, the site needs to be updated to point to the new release: edit the content/filtered-resources/.htaccess file (locally or <a cla
 ss="externalLink" href="https://cms.apache.org/redirect?uri=http://maventest.apache.org/filtered-resources/.htaccess&amp;action=edit">with the CMS</a>) to update rewrite rule</p><div class="source"><pre>RewriteRule ^plugins/maven-XXX-plugin/(.*)$ /plugins/maven-XXX-plugin-Y.Z/$1 [L]</pre></div></div><div class="section"><h3>Updating the Maven site<a name="Updating_the_Maven_site"></a></h3><p>Use the CMS to update <a href="/plugins/">the plugins page</a>, made easy with <a class="externalLink" href="https://cms.apache.org/#bookmark">the CMS bookmarklet</a>.</p></div><div class="section"><h3>idea to be developped if sufficient people is interested<a name="idea_to_be_developped_if_sufficient_people_is_interested"></a></h3><p>Instead of doing command line svn and extpaths.txt + .htaccess edits, the staging/release operations could be automated as web ui like following:</p><ul><li>http://cms.apache.org/maventest/release/plugins/maven-xxx-plugin-X.Y could display a page proposing 
 to <b>stage the release documentation</b> (doing svn command and .htaccess edit)</li><li>next time this page is displayed, with the content already available in svn, the page could propose 2 different actions: <b>drop the staged documentation</b> (with extpaths.txt removal) or <b>publish the release website</b>.</li></ul></div></div>
       </div>
     </div>
     <div class="clear">