You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by hb...@apache.org on 2013/06/26 23:38:06 UTC

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

Author: hboutemy
Date: Wed Jun 26 21:38:06 2013
New Revision: 1497117

URL: http://svn.apache.org/r1497117
Log:
added link to dist-tool-plugin report on CI server

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=1497117&r1=1497116&r2=1497117&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 Wed Jun 26 21:38:06 2013
@@ -160,13 +160,13 @@ I will promote the artifacts to the cent
 
 * 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. Currently this need to be in maven-pmc group. ( See {{{https://issues.apache.org/jira/browse/INFRA-5945}https://issues.apache.org/jira/browse/INFRA-5945}} )  
+  The official Apache release is the 'source-release' bundle. All releases must be copied to {{{http://www.apache.org/dist/maven/}the official 
+  release area}}. The release area is maintained with svnsubpub. To deliver a release, you add it to 
+  {{{https://dist.apache.org/repos/dist/release/maven}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.) Add the release, its signature, and corresponding
+  MD5 files. Currently this requires to be in maven-pmc group (see {{{https://issues.apache.org/jira/browse/INFRA-5945}https://issues.apache.org/jira/browse/INFRA-5945}}).
   For example:
 
 +--------+
@@ -179,6 +179,9 @@ wagon/wagon-2.2-source-release.zip.md5
   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.
 
+  To check that everything is ok in the dist area, dist-tool-plugin has been written and run once a day to produce
+  {{{https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/}following report}}.
+
 * Promote the release
 
  Once the release is deemed fit for public consumption it can be transfered to a production repository where it will