svn commit: r829585 - in /websites/production/cxf/content: cache/main.pageCache release-management.html

[bu...@apache.org]

Author: buildbot
Date: Tue Aug 21 17:47:29 2012
New Revision: 829585

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/main.pageCache
    websites/production/cxf/content/release-management.html

Modified: websites/production/cxf/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/cxf/content/release-management.html
==============================================================================
--- websites/production/cxf/content/release-management.html (original)
+++ websites/production/cxf/content/release-management.html Tue Aug 21 17:47:29 2012
@@ -171,7 +171,7 @@ mvn release:perform
 </div></div>
 <p>That will tag the release, update the poms, etc...  Then build it (off the tag) and deploy everything (including source jars and javadoc jars) to the Nexus repository location and gpg signs everything.  When the build is done staging, you need to login to the Nexus repository and "close" the staging are.    That is very important.   After the staging are is closed, note the URL for the staging area as you will need that for the vote.</p>
 <div class="panelMacro"><table class="warningMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/forbidden.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">You may encounter error like<br clear="none">
-<a shape="rect" class="createlink" href="/confluence/pages/createpage.action?spaceKey=CXF&amp;title=INFO&amp;linkCreation=true&amp;fromPageId=70605">INFO</a> Unable to tag SCM<br clear="none">
+<span class="error">[INFO]</span> Unable to tag SCM<br clear="none">
 Provider message:<br clear="none">
 The svn tag command failed.<br clear="none">
 Command output:<br clear="none">
@@ -185,14 +185,32 @@ will pick up the left task from last run
 <p>At this point, everything "pre-vote" is done.   Call the vote.</p>
 
 
+<h2><a shape="rect" name="ReleaseManagement-Releasingtheartifacts"></a>Releasing the artifacts</h2>
 
-<p>After the vote passes, you'll need to promote that staging repository to the main location. Login to Nexus to do that as well.  See above Maven team release page.</p>
+<ul><li>Maven artifacts -  After the vote passes, you'll need to promote that staging repository to the main location. Login to Nexus to do that as well.  See above Maven team release page.</li></ul>
 
-<p>Also, don't forget to copy the actual distributions to people.apache.org:/www/www.apache.org/dist/cxf.</p>
 
-<p>Unpack the javadocs.  Create a new directory in /www/cxf.apache.org/javadoc to match the version number and then unpack the cxf-bundle/$version/*-javadoc.jar from the maven repo into that new directory.  Update the "latest" sym-links in the javadoc directory to point to the new directory.</p>
+<ul><li>Distributions - You will need to commit the distributions into the special svn distribution area:
+<a shape="rect" class="external-link" href="https://dist.apache.org/repos/dist/release/cxf">https://dist.apache.org/repos/dist/release/cxf</a><br clear="none">
+when the commit done there, they will be live on dist.apache.org fairly quickly, but it will still take time for the mirrors to get copies.   It's likely easier to make the directory via an svn command, check out just that directory, and then add the files.  The dist area is rather large (400MB or so) so checking out the entire thing may be slow. 
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<pre class="code-java">
+svn mkdir https:<span class="code-comment">//dist.apache.org/repos/dist/release/cxf/2.6.3
+</span>svn checkout https:<span class="code-comment">//dist.apache.org/repos/dist/release/cxf/2.6.3
+</span>....  add files to 2.6.3 .....
+svn commit
+</pre>
+</div></div></li></ul>
 
-<p>Finally, update the <a shape="rect" href="download.html" title="Download">download</a> pages.</p>
+
+
+<ul><li>Update the download page - around 24 hours after committing the distributions, update the download page, release notes, etc... to point at the new versions.</li></ul>
+
+
+<ul><li>Unpack the javadocs from the appropriate cxf-bundle-VERSION-javadocs.jar into the appropriate directory in an svn checkout of <a shape="rect" class="external-link" href="https://svn-master.apache.org/repos/infra/websites/production/cxf/content/javadoc">https://svn-master.apache.org/repos/infra/websites/production/cxf/content/javadoc</a>  and commit the new version.  Make sure any new files are added.</li></ul>
+
+
+<ul><li>Unpack the schemas directory from the appropriate cxf-bundle-VERSION.jar and check if any of the schemas in <a shape="rect" class="external-link" href="https://svn-master.apache.org/repos/infra/websites/production/cxf/content/schemas">https://svn-master.apache.org/repos/infra/websites/production/cxf/content/schemas</a> need updating.</li></ul>
 </div>
            </div>
            <!-- Content -->