You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by bu...@apache.org on 2012/12/29 22:25:13 UTC
svn commit: r844255 - in /websites/staging/maven/trunk/content: ./
developers/release/maven-project-release-procedure.html
maven-site-1.0-site.jar
Author: buildbot
Date: Sat Dec 29 21:25:12 2012
New Revision: 844255
Log:
Staging update by buildbot for maven
Modified:
websites/staging/maven/trunk/content/ (props changed)
websites/staging/maven/trunk/content/developers/release/maven-project-release-procedure.html
websites/staging/maven/trunk/content/maven-site-1.0-site.jar
Propchange: websites/staging/maven/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Dec 29 21:25:12 2012
@@ -1 +1 @@
-1426830
+1426837
Modified: websites/staging/maven/trunk/content/developers/release/maven-project-release-procedure.html
==============================================================================
--- websites/staging/maven/trunk/content/developers/release/maven-project-release-procedure.html (original)
+++ websites/staging/maven/trunk/content/developers/release/maven-project-release-procedure.html Sat Dec 29 21:25:12 2012
@@ -271,7 +271,10 @@ The vote has passed with the following r
+1 (binding): <<list of names>>
+1 (non binding): <<list of names>>
-I will promote the artifacts to the central repo.</pre></div><p>If the vote is unsuccessful, the process will need to be restarted. Be sure to drop your staging repository as described in <a class="externalLink" href="http://www.apache.org/dev/publishing-maven-artifacts.html#drop">Dropping a Repo</a>.</p></div><div class="section"><h3>Promote the release<a name="Promote_the_release"></a></h3><p>Once the release is deemed fit for public consumption it can be transfered to a production repository where it will be available to all users.</p><ol style="list-style-type: decimal"><li>See <a class="externalLink" href="http://www.apache.org/dev/publishing-maven-artifacts.html#promote">Promoting a Repo</a> for details on promotion.</li><li>Deploy the current website<p>As above, deploy the web site if appropriate and update the project site for the new release.</p></li><li>Update the version tracking in JIRA<p>In the relevant project, go to Administration, then Versions. Mark the <tt>
Y.Z</tt> version as 'released'. Create version <tt>Y.Z+1</tt>, if that hasn't already been done. You may also archive any deprecated releases (milestones or alphas) at this time.</p></li><li>Wait for everything to sync<ol style="list-style-type: lower-alpha"><li>Sync to Maven Central<p>The sync into central staging from repository.apache.org occurs every 4 hours. There is a separate hourly schedule that runs which pushes from staging to the other central machines, and then updates the indexes.</p></li><li>Sync to Maven Website<p>Until the svnpubsub work is complete, the deployment of the Maven website will <a class="externalLink" href="http://www.apache.org/dev/release-publishing.html#sync-delay">take an hour or so to sync</a>.</p></li></ol></li><li>Create an announcement.<ol style="list-style-type: lower-alpha"><li>Using Maven Changes Plugin<p>If you are releasing a plugin or a shared component you can let Maven Changes Plugin <b>generate</b>, and eventually even <b>send</b
>, the announcement for you. First make sure that you have configured the necessary properties in your <a href="../committer-settings.html">committer settings</a>.</p><div class="source"><pre>cd target/checkout
+I will promote the artifacts to the central repo.</pre></div><p>If the vote is unsuccessful, the process will need to be restarted. Be sure to drop your staging repository as described in <a class="externalLink" href="http://www.apache.org/dev/publishing-maven-artifacts.html#drop">Dropping a Repo</a>.</p></div><div class="section"><h3>Copy the source release to the Apache Distribution Area<a name="Copy_the_source_release_to_the_Apache_Distribution_Area"></a></h3><p>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.</p><p>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:</p><div class="source"><pre>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</pre></div><p>You should also run 'svn rm' as needed to clear out older releases. As per <a class="externalLink" href="http://www.apache.org/dev/release.html#where-do-releases-go">the policy</a>, 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.</p></div><div class="section"><h3>Promote the release<a name="Promote_the_release"></a></h3><p>Once the release is deemed fit for public consumption it can be transfered to a production repository where it will be available to all users.</p><ol style="list-style-type: decimal"><li>See <a class="externalLink" href="http://www.apache.org/dev/publishing-maven-artifacts.html#promote">Promoting a Repo</a> for details on promotion.</li><li>Deploy the current website<p>As above, deploy the web site if appropriate and update the project site for the new release.</p></li
><li>Update the version tracking in JIRA<p>In the relevant project, go to Administration, then Versions. Mark the <tt>Y.Z</tt> version as 'released'. Create version <tt>Y.Z+1</tt>, if that hasn't already been done. You may also archive any deprecated releases (milestones or alphas) at this time.</p></li><li>Wait for everything to sync<ol style="list-style-type: lower-alpha"><li>Sync to Maven Central<p>The sync into central staging from repository.apache.org occurs every 4 hours. There is a separate hourly schedule that runs which pushes from staging to the other central machines, and then updates the indexes.</p></li><li>Sync to Maven Website<p>Until the svnpubsub work is complete, the deployment of the Maven website will <a class="externalLink" href="http://www.apache.org/dev/release-publishing.html#sync-delay">take an hour or so to sync</a>.</p></li></ol></li><li>Create an announcement.<ol style="list-style-type: lower-alpha"><li>Using Maven Changes Plugin<p>If you are rel
easing a plugin or a shared component you can let Maven Changes Plugin <b>generate</b>, and eventually even <b>send</b>, the announcement for you. First make sure that you have configured the necessary properties in your <a href="../committer-settings.html">committer settings</a>.</p><div class="source"><pre>cd target/checkout
mvn changes:announcement-mail -Papache-release</pre></div><p>Even if mail send fails, generated annoucement is available in <tt>target/annoucement</tt> (see <tt>annoucement.vm</tt>): you can use it as a base for sending the mail manually.</p><p>If your SMTP server requires authentication you need to add the command line options for it:</p><div class="source"><pre>cd target/checkout
mvn changes:announcement-mail -Dchanges.username=<SMTP-USERNAME> -Dchanges.password=<SMTP-PASSWORD> -Papache-release</pre></div></li><li>Manually<p><b>Note:</b> You must send this email from your apache email account, e.g. YOUR_APACHE_USERNAME@apache.org otherwise the email to announce@maven.apache.org will bounce.</p><div class="source"><pre>From: YOUR_APACHE_USERNAME@apache.org
To: announce@maven.apache.org, users@maven.apache.org
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.