You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by iv...@apache.org on 2011/04/01 02:36:03 UTC
svn commit: r1087526 - in /wicket/common/site/trunk:
_site/contribute/release.html contribute/release.md
Author: ivaynberg
Date: Fri Apr 1 00:36:03 2011
New Revision: 1087526
URL: http://svn.apache.org/viewvc?rev=1087526&view=rev
Log:
added code to post to mirrors
Modified:
wicket/common/site/trunk/_site/contribute/release.html
wicket/common/site/trunk/contribute/release.md
Modified: wicket/common/site/trunk/_site/contribute/release.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/contribute/release.html?rev=1087526&r1=1087525&r2=1087526&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/contribute/release.html (original)
+++ wicket/common/site/trunk/_site/contribute/release.html Fri Apr 1 00:36:03 2011
@@ -173,75 +173,94 @@
</ul>
<p>Make sure your <code>~/.m2/settings.xml</code> contains the following definition</p>
+<div class='highlight'><pre><code class='console'><span class='go'><?xml version="1.0"?></span>
+<span class='go'><settings></span>
+<span class='go'><servers></span>
+<span class='go'> <server></span>
+<span class='go'> <id>apache.releases.https</id></span>
+<span class='go'> <username>$your_apache_username</username></span>
+<span class='go'> <password>$your_apache_password</password></span>
+<span class='go'> </server></span>
+<span class='go'></servers></span>
+<span class='go'></settings></span>
+</code></pre>
+</div>
+<ul>
+<li>create a release branch to do your release work in (modifying poms, etc)</li>
+
+<li>then checkout that release branch and cd into it</li>
+</ul>
+<div class='highlight'><pre><code class='console'><span class='gp'>$</span> svn cp https://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.x <span class='se'>\</span>
+<span class='go'>https://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.13 \</span>
+<span class='go'>-m "creating 1.4.13 release branch"</span>
+<span class='go'>Committed revision 1027818.</span>
+<span class='gp'>$</span> <span class='nb'>cd</span> ..
+<span class='gp'>$</span> svn co https://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.13
+<span class='go'>... lots of output ...</span>
+<span class='go'>Checked out revision 1027818.</span>
+<span class='gp'>$</span> <span class='nb'>cd </span>wicket-1.4.13
+</code></pre>
+</div>
+<ul>
+<li>Set correct version in the pom files using the <a href='http://mojo.codehaus.org/versions-maven-plugin'>maven-versions-plugin</a>:</li>
+</ul>
+<div class='highlight'><pre><code class='console'><span class='go'>mvn versions:set -DnewVersion=1.4.13</span>
+<span class='go'>... list of all changed artifacts changed.</span>
+<span class='go'>mvn versions:commit </span>
+<span class='go'>removes all of the pom.xml.versionsBackup files.</span>
+</code></pre>
+</div>
+<ul>
+<li>Call release.sh (still from the checkout out release branch code) <strong>NOTE</strong> If you get an error while generating javadocs like ”<code>java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl</code>”, run a <code>mvn clean install -Dmaven.test.skip=true</code> followed by a <code>mvn javadoc:jar</code>, then re-run <code>release.sh</code>.</li>
+
+<li>Login to the Apache Nexus Repository on http://repository.apache.org; See <a href='#nexus'>Releasing with Apache Nexus</a> below.</li>
+
+<li>Select <strong>Staging Repositories</strong> from the left hand side, then select the repository and click <strong>Close</strong>.</li>
+
+<li>Test that the distribution (examples, rat, etc) is accessible from the staging repository url.</li>
+
+<li>upload non-maven artifacts to pao:</li>
+</ul>
+<div class='highlight'><pre><code class='console'><span class='go'>export wicketversion=<version></span>
+<span class='go'>svn export http://svn.apache.org/repos/asf/wicket/common/KEYS target/dist/KEYS</span>
+<span class='go'>ssh people.apache.org mkdir public_html/wicket-$wicketversion</span>
+<span class='go'>scp -r target/dist target/m2-repo people.apache.org:public_html/wicket-$wicketversion</span>
+</code></pre>
+</div>
+<ul>
+<li>Commit these modified pom files to the release branch.</li>
+<li>Send vote message to dev@ mailing list. Include link to the closed repository for testing against.</li>
+
+<li>Wait requisite 72 hours for the vote to pass (we hope)</li>
+
+<li>Copy release to apache mirrors</li>
+</ul>
+<div class='highlight'><pre><code class='console'><span class='go'>ssh people.apache.org</span>
+<span class='go'>mkdir /www/www.apache.org/dist/wicket/1.4.0</span>
+<span class='go'>mv ~/public_html/wicket-1.4.0/dist/* /www/www.apache.org/dist/wicket/1.4.0</span>
+<span class='go'>chown -R :wicket /www/www.apache.org/dist/wicket/1.4.0</span>
+</code></pre>
+</div>
+<ul>
+<li>Login to repository.apache.org, select the closed repository and click <strong>Release</strong>. It will be accessible immediately through the apache release repo and then within 1-2 hours through maven central.</li>
+
+<li>If the release is voted down you can <strong>Drop</strong> the staged release and then restage later after incorporating the necessary changes.</li>
+
+<li>Tag the release in SVN:</li>
+</ul>
+<div class='highlight'><pre><code class='console'><span class='gp'>$</span> svn cp https://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.13 <span class='se'>\</span>
+<span class='go'>https://svn.apache.org/repos/asf/wicket/releases/wicket-1.4.13 \</span>
+<span class='go'>-m "tag release 1.4.13"</span>
+<span class='go'>Committed revision 1027826.</span>
+</code></pre>
+</div>
<ul>
-<li>
-<p>create a release branch to do your release work in (modifying poms, etc)</p>
-</li>
-
-<li>
-<p>then checkout that release branch and cd into it</p>
-</li>
-
-<li>
-<p>Set correct version in the pom files using the <a href='http://mojo.codehaus.org/versions-maven-plugin'>maven-versions-plugin</a>:</p>
-</li>
-
-<li>
-<p>Call release.sh (still from the checkout out release branch code) <strong>NOTE</strong> If you get an error while generating javadocs like ”<code>java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl</code>”, run a <code>mvn clean install -Dmaven.test.skip=true</code> followed by a <code>mvn javadoc:jar</code>, then re-run <code>release.sh</code>.</p>
-</li>
-
-<li>
-<p>Login to the Apache Nexus Repository on http://repository.apache.org; See <a href='#nexus'>Releasing with Apache Nexus</a> below.</p>
-</li>
-
-<li>
-<p>Select <strong>Staging Repositories</strong> from the left hand side, then select the repository and click <strong>Close</strong>.</p>
-</li>
-
-<li>
-<p>Test that the distribution (examples, rat, etc) is accessible from the staging repository url.</p>
-</li>
-
-<li>
-<p>upload non-maven artifacts to pao:</p>
-</li>
-
-<li>
-<p>Commit these modified pom files to the release branch.</p>
-</li>
-
-<li>
-<p>Send vote message to dev@ mailing list. Include link to the closed repository for testing against.</p>
-</li>
-
-<li>
-<p>Wait requisite 72 hours for the vote to pass (we hope)</p>
-</li>
-
-<li>
-<p>Login to repository.apache.org, select the closed repository and click <strong>Release</strong>. It will be accessible immediately through the apache release repo and then within 1-2 hours through maven central.</p>
-</li>
-
-<li>
-<p>If the release is voted down you can <strong>Drop</strong> the staged release and then restage later after incorporating the necessary changes.</p>
-</li>
-
-<li>
-<p>Tag the release in SVN:</p>
-</li>
-
-<li>
-<p>Wait until repo1.maven.org has picked up the release artifacts.</p>
-</li>
-
-<li>
-<p>Wait 24 hours until mirrors picked up release artifacts</p>
-</li>
-
-<li>
-<p>Announce (see <a href='#announcing'>below</a>)</p>
-</li>
+<li>Wait until repo1.maven.org has picked up the release artifacts.</li>
+
+<li>Wait 24 hours until mirrors picked up release artifacts</li>
+
+<li>Announce (see <a href='#announcing'>below</a>)</li>
</ul>
<h2 id='nexus'>Staging Releases using the Apache Nexus Repository</h2>
@@ -257,7 +276,18 @@
<p>The <code><id></code> of the staging repository is: <strong>apache.releases.https</strong>.</p>
<p>Place a <code><server></code> definition in your <code>~/.m2/settings.xml</code> file like this:</p>
-
+<div class='highlight'><pre><code class='console'><span class='go'><?xml version="1.0"?></span>
+<span class='go'><settings></span>
+<span class='go'><servers></span>
+<span class='go'> <server></span>
+<span class='go'> <id>apache.releases.https</id></span>
+<span class='go'> <username>$username</username></span>
+<span class='go'> <password>$password</password></span>
+<span class='go'> </server></span>
+<span class='go'></servers></span>
+<span class='go'></settings></span>
+</code></pre>
+</div>
<p>This works if you can deploy artifacts into the repository.apache.org properly (i.e. you don’t see failures mentioning 401 errors).</p>
<h3 id='managing_staged_artifacts'>Managing Staged Artifacts</h3>
@@ -281,7 +311,12 @@
<h2 id='announcing'>Announcing the release</h2>
<p>Edit the _config.yaml file. This file contains a site wide configuration section specific to Wicket:</p>
-
+<div class='highlight'><pre><code class='yaml'><span class='l-Scalar-Plain'>wicket</span><span class='p-Indicator'>:</span>
+ <span class='l-Scalar-Plain'>version</span><span class='p-Indicator'>:</span> <span class='l-Scalar-Plain'>1.4.10</span>
+ <span class='l-Scalar-Plain'>released</span><span class='p-Indicator'>:</span> <span class='l-Scalar-Plain'>2010-08-11</span>
+ <span class='l-Scalar-Plain'>versions</span><span class='p-Indicator'>:</span> <span class='p-Indicator'>[</span><span class='nv'>1.3.7</span><span class='p-Indicator'>,</span> <span class='nv'>1.3-SNAPSHOT</span><span class='p-Indicator'>,</span> <span class='nv'>1.4.9</span><span class='p-Indicator'>,</span> <span class='nv'>1.4.10</span><span class='p-Indicator'>,</span> <span class='nv'>1.4-SNAPSHOT</span><span class='p-Indicator'>,</span> <span class='nv'>1.5-M1</span><span class='p-Indicator'>,</span> <span class='nv'>1.5-SNAPSHOT</span><span class='p-Indicator'>]</span>
+</code></pre>
+</div>
<p>You’ll need to edit this part: modify the version, update the released date, and add the new version to the versions list (remove any stale releases, typically just leave the previous release as well).</p>
<ul>
@@ -299,6 +334,16 @@
<ul>
<li>Commit the JavaDocs to <a href='https://svn.apache.org/repos/asf/wicket/common/site/apidocs/1.4'>https://svn.apache.org/repos/asf/wicket/common/site/apidocs/1.4</a> svnpubsub will push this directly to our website. (example script below)</li>
</ul>
+<div class='highlight'><pre><code class='console'><span class='gp'>#</span> <span class='k'>do </span>this in your locally-checked-out release branch <span class='o'>(</span>i.e. svn.../releases/wicket-1.4.13<span class='o'>)</span>
+<span class='go'>mvn javadoc:aggregate</span>
+<span class='gp'>#</span> note that you may need to tweak these paths to fit your configuration:
+<span class='go'>cp -r target/site/apidocs/* ../wicket-common/site/apidocs/1.4/</span>
+<span class='go'>cd ../wicket-common/</span>
+<span class='gp'>#</span> call <span class='s2'>"svn add"</span> <span class='k'>for </span>files that are new <span class='o'>(</span>there<span class='err'>'</span>s probably an easier way to <span class='k'>do </span>this<span class='o'>)</span>
+<span class='go'>svn stat | grep -e '^?' | sed 's/\?\W*//' | xargs svn add</span>
+<span class='go'>svn commit -m "changes to update javadocs to latest release"</span>
+</code></pre>
+</div>
</div>
<div id="clearer"></div>
<div id="footer"><span>
Modified: wicket/common/site/trunk/contribute/release.md
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/contribute/release.md?rev=1087526&r1=1087525&r2=1087526&view=diff
==============================================================================
--- wicket/common/site/trunk/contribute/release.md (original)
+++ wicket/common/site/trunk/contribute/release.md Fri Apr 1 00:36:03 2011
@@ -71,6 +71,13 @@ scp -r target/dist target/m2-repo people
* Commit these modified pom files to the release branch.
* Send vote message to dev@ mailing list. Include link to the closed repository for testing against.
* Wait requisite 72 hours for the vote to pass (we hope)
+* Copy release to apache mirrors
+{% highlight console %}
+ssh people.apache.org
+mkdir /www/www.apache.org/dist/wicket/1.4.0
+mv ~/public_html/wicket-1.4.0/dist/* /www/www.apache.org/dist/wicket/1.4.0
+chown -R :wicket /www/www.apache.org/dist/wicket/1.4.0
+{% endhighlight %}
* Login to repository.apache.org, select the closed repository and click **Release**. It will be accessible immediately through the apache release repo and then within 1-2 hours through maven central.
* If the release is voted down you can **Drop** the staged release and then restage later after incorporating the necessary changes.
* Tag the release in SVN: