svn commit: r1426837 - /maven/site/trunk/content/apt/developers/release/maven-project-release-procedure.apt

[bi...@apache.org]

Author: bimargulies
Date: Sat Dec 29 21:23:31 2012
New Revision: 1426837

URL: http://svn.apache.org/viewvc?rev=1426837&view=rev
Log:
Document the requirement to put releases into the dist area.

Modified:
    maven/site/trunk/content/apt/developers/release/maven-project-release-procedure.apt

Modified: maven/site/trunk/content/apt/developers/release/maven-project-release-procedure.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/content/apt/developers/release/maven-project-release-procedure.apt?rev=1426837&r1=1426836&r2=1426837&view=diff
==============================================================================
--- maven/site/trunk/content/apt/developers/release/maven-project-release-procedure.apt (original)
+++ maven/site/trunk/content/apt/developers/release/maven-project-release-procedure.apt Sat Dec 29 21:23:31 2012
@@ -157,6 +157,27 @@ I will promote the artifacts to the cent
   If the vote is unsuccessful, the process will need to be restarted. Be sure to drop your staging repository as
   described in {{{http://www.apache.org/dev/publishing-maven-artifacts.html#drop}Dropping a Repo}}.
 
+* Copy the source release to the Apache Distribution Area
+
+  The official Apache release is the 'source-release' bundle. All releases must be copied to the official 
+  release area. The release area is maintained with svnsubpub. To deliver a release, you add it to 
+  the subversion repository for the dist area.
+
+  The Maven dist area is https://dist.apache.org/repos/dist/release/maven. In here, you will
+  find a series of subdirectories (plugins, scm, etc, etc.) Add the release, its signatures, and corresponding
+  MD5 files. For example:
+
++--------+
+wagon/wagon-2.2-source-release.zip
+wagon/wagon-2.2-source-release.zip.asc
+wagon/wagon-2.2-source-release.zip.asc.md5
+wagon/wagon-2.2-source-release.zip.md5
++--------+
+
+  You should also run 'svn rm' as needed to clear out older releases.  As per {{{http://www.apache.org/dev/release.html#where-do-releases-go}the policy}},
+  only the latest release on a branch should stay in the main dist areas. So long as the previous release is at least a day old, the automatic archiver
+  will have copied it to the archive.
+
 * Promote the release
 
  Once the release is deemed fit for public consumption it can be transfered to a production repository where it will
@@ -260,4 +281,4 @@ Enjoy,
  This might also be a step to take if other shared resources are released, or if plugin releases are
  of particular interest to that group.
 
- [[7]] Celebrate :o)
+ [[7]] Celebrate :o)
\ No newline at end of file