cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r830375 - in /websites/production/cxf/content: cache/main.pageCache release-management.html
Date Tue, 28 Aug 2012 19:47:25 GMT
Author: buildbot
Date: Tue Aug 28 19:47:24 2012
New Revision: 830375

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 28 19:47:24 2012
@@ -201,12 +201,12 @@ will pick up the left task from last run
 
 <h2><a shape="rect" name="ReleaseManagement-Releasingtheartifacts"></a>Releasing
the artifacts</h2>
 
-<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>
+<ul><li>Maven artifacts -  After the vote passes, you'll need to promote that
staging repository to the main location. Login to <a shape="rect" class="external-link"
href="https://repository.apache.org">Nexus repository location</a> to do that as
well, find the staging repository and click the Release button.</li></ul>
 
 
 <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. 
+after you commit 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
@@ -217,8 +217,9 @@ svn commit
 </div></div></li></ul>
 
 
+<p>The <a shape="rect" href="http://cxf.apache.org/download.html">download page</a>
of a currently released version will tell you the precise files you need to upload.  Basically,
the -src.tar.gz, -src.zip, tar.gz, .zip files, and the .md5, .sha1, and .asc signature files
of each of those.  For greatest accuracy, it's best to download the files from Nexus and use
those.  (For example, for CXF 2.6.2, you would check <a shape="rect" class="external-link"
href="https://repository.apache.org/content/repositories/releases/org/apache/cxf/apache-cxf/2.6.2/">this
folder</a>).  </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>Update the download page - around 24 hours after committing the distributions,
update the download page, release notes, etc. to point at the new versions.  At that stage
you'll want to delete (svn rm) the previous version of each branch you uploaded to <a shape="rect"
class="external-link" href="https://dist.apache.org">https://dist.apache.org</a>,
so if you added <a shape="rect" class="external-link" href="https://dist.apache.org/repos/dist/release/cxf/2.6.3">https://dist.apache.org/repos/dist/release/cxf/2.6.3</a>
and <a shape="rect" class="external-link" href="https://dist.apache.org/repos/dist/release/cxf/2.5.6">https://dist.apache.org/repos/dist/release/cxf/2.5.6</a>,
you'll want to remove <a shape="rect" class="external-link" href="https://dist.apache.org/repos/dist/release/cxf/2.6.2">https://dist.apache.org/repos/dist/release/cxf/2.6.2</a>
and <a shape="rect" class="external-link" href="https://dist.apache.org/repos/dist/release/cxf/2.5.5">https://dist.apache.
 org/repos/dist/release/cxf/2.5.5</a>.  (Older versions will still be available at <a
shape="rect" class="external-link" href="http://archive.apache.org/dist/cxf/">http://archive.apache.org/dist/cxf/</a>
and are referenced from there on the CXF download page.)</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>



Mime
View raw message