You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@commons.apache.org by bu...@apache.org on 2013/03/23 21:13:47 UTC
svn commit: r855710 - in /websites/staging/commons/trunk/content: ./
releases/release.html
Author: buildbot
Date: Sat Mar 23 20:13:47 2013
New Revision: 855710
Log:
Staging update by buildbot for commons
Modified:
websites/staging/commons/trunk/content/ (props changed)
websites/staging/commons/trunk/content/releases/release.html
Propchange: websites/staging/commons/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Mar 23 20:13:47 2013
@@ -1 +1 @@
-1460196
+1460220
Modified: websites/staging/commons/trunk/content/releases/release.html
==============================================================================
--- websites/staging/commons/trunk/content/releases/release.html (original)
+++ websites/staging/commons/trunk/content/releases/release.html Sat Mar 23 20:13:47 2013
@@ -183,10 +183,11 @@
</p><ul>
<li>
The signed release candidate source and binary distributions and release notes are available
- in ~/public_html/commons-foo-1.2-RC3.
+ in https://dist.apache.org/repos/dist/dev/commons/foo.
</li>
<li>
- The maven artifacts associated with the release are available in ~/public_html/commons-foo-1.2-RC3/maven.
+ The maven artifacts associated with the release are available in a closed Nexus staging
+ repository.
</li>
</ul>
@@ -194,31 +195,35 @@
<div class="section"><h3>1 Move Releases Into Distribution Directories<a name="a1_Move_Releases_Into_Distribution_Directories"></a></h3>
<p>
- On people.apache.org, change directory to the distribution directory for your component:
- </p><div><pre>
- cd /www/www.apache.org/dist/commons/foo/ </pre></div>
-
- <p>
- Move source distributions, their detached signatures and md5 sums into position.
- All source versions live in the <i>source</i> subdirectory.
- </p><div><pre>
- mv ~/public_html/foo-1.2-RC3/commons-foo-1.2-src* source </pre></div>
-
- <p>
- Move the binary distributions, their detached signatures and md5 sums into position.
- All binary versions live in the <i>binaries</i> subdirectory.
- [Note: the source must have been moved already, otherwise the following command will
- also be applied to the source files.]
- </p><div><pre>
- mv ~/public_html/foo-1.2-RC3/commons-foo-1.2* binaries </pre></div>
-
- <p>
- Double check the permissions for both binaries and source distributions.
- The file permissions should be "-rw-rw-r--" and the group should be "commons", for example:
- </p><div><pre>
- -rw-rw-r-- 1 userid commons 203 Feb 21 23:45 commons-foo-1.2-src.tar.gz.asc
+ The distribution area of commons releases is populated from
+ <a class="externalLink" href="https://dist.apache.org/repos/dist/release/commons/">https://dist.apache.org/repos/dist/release/commons/</a>
+ via svnpubsub. In order to publish the release, you must move the distributions files
+ from <tt>dev</tt> to <tt>release</tt>.
+ </p>
+ <p>You can perform multiple <tt>svn mv</tt> operations (with or without local
+ working copies) or you can use <a class="externalLink" href="http://svnbook.red-bean.com/en/1.8/svn.ref.svnmucc.re.html">svnmucc</a>,
+ for example:</p>
+ <div><pre>
+ svnmucc -U https://dist.apache.org/repos/dist \
+ mv dev/commons/foo/RELEASE-NOTES.txt release/commons/foo \
+ mv dev/commons/foo/binaries/commons-foo-1.2-bin.tar.gz release/commons/foo/binaries \
+ mv dev/commons/foo/binaries/commons-foo-1.2-bin.tar.gz.asc release/commons/foo/binaries \
+ mv dev/commons/foo/binaries/commons-foo-1.2-bin.tar.gz.md5 release/commons/foo/binaries \
+ mv dev/commons/foo/binaries/commons-foo-1.2-bin.tar.gz.asc release/commons/foo/binaries \
+ mv dev/commons/foo/binaries/commons-foo-1.2-bin.zip release/commons/foo/binaries \
+ mv dev/commons/foo/binaries/commons-foo-1.2-bin.zip.asc release/commons/foo/binaries \
+ mv dev/commons/foo/binaries/commons-foo-1.2-bin.zip.md5 release/commons/foo/binaries \
+ mv dev/commons/foo/binaries/commons-foo-1.2-bin.zip.asc release/commons/foo/binaries \
+ mv dev/commons/foo/source/commons-foo-1.2-src.tar.gz release/commons/foo/source \
+ mv dev/commons/foo/source/commons-foo-1.2-src.tar.gz.asc release/commons/foo/source \
+ mv dev/commons/foo/source/commons-foo-1.2-src.tar.gz.md5 release/commons/foo/source \
+ mv dev/commons/foo/source/commons-foo-1.2-src.tar.gz.asc release/commons/foo/source \
+ mv dev/commons/foo/source/commons-foo-1.2-src.zip release/commons/foo/source \
+ mv dev/commons/foo/source/commons-foo-1.2-src.zip.asc release/commons/foo/source \
+ mv dev/commons/foo/source/commons-foo-1.2-src.zip.md5 release/commons/foo/source \
+ mv dev/commons/foo/source/commons-foo-1.2-src.zip.asc release/commons/foo/source \
+ -m "Publish commons-foo 1.2 Release"
</pre></div>
-
</div>
<div class="section"><h3>2 Update Release Directory<a name="a2_Update_Release_Directory"></a></h3>
@@ -229,14 +234,12 @@
If this document is not present, then copy one from an existing release directory
and edit that.
</p>
+ <p>The README must be https://dist.apache.org/repos/dist/release/commons/foo/README.html</p>
<p>
Update the latest release number. Please also read through and correct any mistakes you find
and fix other items (eg. urls) which need updating.
</p>
<p>
- Copy the revised <tt>README.html</tt> into the binary and source directories, replacing any old versions.
- </p>
- <p>
<a name="Check_KEYS_file"></a>
<b>Check KEYS file</b><br />
Check the <tt>KEYS</tt> file located in the main release directory. This should contain all the
@@ -244,85 +247,22 @@
that it contains the public key you've used to sign these releases. The <tt>KEYS</tt> file
gives instructions on how to do this.
</p>
- <p>
- <b>Symbolic Links</b><br />
- These are no longer to be used, so please
- <a class="externalLink" href="http://www.apache.org/dev/mirror-step-by-step.html#symbolic_links">do not use symbolic links in mirrored directories!</a>
- <b>Update RELEASE-NOTES</b><br />
- Replace the current <tt>RELEASE-NOTES.txt</tt> with the new release notes.
- </p><div><pre>
- mv ~/public_html/foo-1.2-RC3/RELEASE-NOTES.txt .
- </pre></div>
-
</div>
<div class="section"><h3>3 Deploy Maven Artifacts<a name="a3_Deploy_Maven_Artifacts"></a></h3>
- <p>
- Download maven-metadata.xml for commons foo from repo1.maven.org. This file is located in the top-level
- directory for the component. The file should contain a <tt>versioning</tt> element, similar to the following:
- </p><div><pre>
- <versioning>
- <release>1.1</release>
- <versions>
- <version>1.0</version>
- <version>1.1</version>
- </versions>
- <lastUpdated>20091011214529</lastUpdated>
- </versioning> </pre></div>
-
- <p>
- Create a <tt>version</tt> element for 1.2, update the <tt>release</tt> version and update
- the date in the <tt>lastUpdated</tt> element:
- </p><div><pre>
- <versioning>
- <release>1.2</release>
- <versions>
- <version>1.0</version>
- <version>1.1</version>
- <version>1.2</version>
- </versions>
- <lastUpdated>20100401214529</lastUpdated>
- </versioning> </pre></div>
-
- <p>
- Create the hash files, maven-metadata.xml.sha1 and maven-metadata.xml.md5 for the updated metadata file.
- If you do not have openssl or another suitable utility installed locally, you can upload the edited
- maven-metadata.xml file to people.apache.org and use the following commands to create these files:
- </p><div><pre>
- md5 -q maven-metadata.xml > maven-metadata.xml.md5
- sha1 -q maven-metadata.xml > maven-metadata.xml.sha1 </pre></div>
-
- <p>
- Your Maven artifacts (jar and pom files with hashes and signatures) should be placed in
- <tt>/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/commons/commons-foo/1.2/</tt> on
- people.apache.org. This assumes that your component has been migrated to use the org.apache.commons groupId.
- If the component still uses commons-foo as its groupId, the deployment location should be
- /www/people.apache.org/repo/m2-ibiblio-rsync-repository/commons-foo/commons-foo/1.2. If your RC directory
- includes a "maven" subdirectory including the maven artifacts, you can move the maven artifacts using
- the following commands (assuming the org.apache.commons groupId):
- </p><div><pre>
- mkdir /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/commons/commons-foo/1.2
- chgrp commons ~/public_html/foo-1.2-RC3/maven/*
- chmod g+w ~/public_html/foo-1.2-RC3/maven/*
- mv ~/public_html/foo-1.2-RC3/maven/* /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/commons/commons-foo/1.2 </pre></div>
-
- <p>
- Double-check permissions on the newly created directory and the deployed files. Also double-check that all
- of the artifacts have hashes and signature files associated with them.
- </p>
- <p>
- The updated <tt>maven-metadata.xml</tt> and its sha1 and md5 hashes should be placed in the directory
- above the deployed artifacts
- (<tt>/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/commons/commons-foo</tt> if
- org.apache.commons is the groupId).
- </p>
+ <p>Login to the Nexus web interface, select your staging repository and
+ <a class="externalLink" href="http://www.apache.org/dev/publishing-maven-artifacts.html#promote">promote</a> it.</p>
<p>
The files placed here will be mirrored (after some delay) to the public distribution
repository on <a class="externalLink" href="http://repo1.maven.org/maven2/">http://repo1.maven.org/maven2/</a>.
</p>
</div>
- <div class="section"><h3>4 Test Main Site Downloads<a name="a4_Test_Main_Site_Downloads"></a></h3>
+ <div class="section"><h3>4 Create Subversion Tag for the Final Release<a name="a4_Create_Subversion_Tag_for_the_Final_Release"></a></h3>
+ <p>Copy the release candidate tag in subversion to a name without RC in its name.</p>
+ </div>
+
+ <div class="section"><h3>5 Test Main Site Downloads<a name="a5_Test_Main_Site_Downloads"></a></h3>
<p>
Wait until the release files are available from the main Apache web site
(<tt>http://www.apache.org/dist/commons/foo/</tt>), then confirm things are good.
@@ -350,7 +290,7 @@
</p>
</div>
- <div class="section"><h3>5 Update Component Build and Website<a name="a5_Update_Component_Build_and_Website"></a></h3>
+ <div class="section"><h3>6 Update Component Build and Website<a name="a6_Update_Component_Build_and_Website"></a></h3>
<ul>
<li>
<b>Update trunk version</b>
@@ -366,7 +306,7 @@
</ul>
</div>
- <div class="section"><h3>6 Create Announcements<a name="a6_Create_Announcements"></a></h3>
+ <div class="section"><h3>7 Create Announcements<a name="a7_Create_Announcements"></a></h3>
<p>
Announce the availability of the new release.
</p>
@@ -380,7 +320,7 @@
</p><ol style="list-style-type: decimal">
<li>The release artifacts are available on the mirrors.</li>
<li>The component website including the updated download page has been updated on the public site
- http://commons.apache.org/foo.</li>
+ http://commons.apache.org/proper/foo.</li>
<li>If the component publishes maven artifacts, these artifacts have been replicated to the central
maven repo at repo1.maven.org. (Clear your local repo of the release artifacts and either activate
the clirr report with the updated version info or update a local project with a dependency to the new
@@ -398,7 +338,7 @@
</div>
- <div class="section"><h3>7 Post Release Cleanup<a name="a7_Post_Release_Cleanup"></a></h3>
+ <div class="section"><h3>8 Post Release Cleanup<a name="a8_Post_Release_Cleanup"></a></h3>
<p>
That's it! The release is out there - but there is still some tidying up to be done.
</p>
@@ -408,9 +348,10 @@
Unless old versions are especially required, remove them from the dist directory. This
will cause the files to also be deleted from the mirrors and
save them some diskspace as well as simplifying things for users.
- Note that the contents of the /www/www.apache.org/dist directory is regularly copied to
- /www/archive.apache.org/dist and from there transferred to host archive.apache.org.
- Deleting files from the standard distribution directories does <i>not</i> delete
+ Note that the contents of the http://www.apache.org/dist directory is regularly copied to
+ http://archive.apache.org/dist.
+ Deleting files from the standard distribution directories
+ on https://dist.apache.org/repos/dist/release/commons/ does <i>not</i> delete
them from the archive dist directories so users will
still be able to access old files even when they are not available from the mirrors.
</li>
@@ -424,7 +365,7 @@
<li>
<b>Update DOAP file</b>
Update the component's <a class="externalLink" href="http://projects.apache.org/guidelines.html">DOAP file</a>
- with details of the released version:
+ and add a new entry with details of the released version:
<div><pre>
<release>
<Version>