Author: dashorst
Date: Thu Aug 12 22:19:47 2010
New Revision: 985015
URL: http://svn.apache.org/viewvc?rev=985015&view=rev
Log:
Added announce section to release guide
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=985015&r1=985014&r2=985015&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/contribute/release.html (original)
+++ wicket/common/site/trunk/_site/contribute/release.html Thu Aug 12 22:19:47
2010
@@ -87,7 +87,7 @@
<ul>
<li>
<a
href="http://www.apache.org/dyn/closer.cgi/wicket/1.4.10";>Wicket 1.4</a>
- (<a href="http://wicket.apache.org/apidocs/1.4";
title="JavaDocs of the latest stable release - 1.4.10">docs</a>)
+ (<a href="http://wicket.apache.org/apidocs/1.4";
title="JavaDocs of the latest stable release - 1.4.x">docs</a>)
</li>
<li>
<a
href="http://www.apache.org/dyn/closer.cgi/wicket/1.3.7";>Wicket 1.3</a>
@@ -144,7 +144,23 @@
<div id="contentbody">
<h1>Build a release</h1>
- <h2 id='releasing_apache_wicket_14x'>Releasing Apache
Wicket 1.4.x</h2>
+ <h2 id='contents'>Contents</h2>
+
+<ul>
+<li><a href='#release-14'>Releasing Apache Wicket 1.4.x</a></li>
+
+<li><a href='#release-13'>Releasing Apache Wicket 1.3.x</a></li>
+
+<li><a href='#mirrors'>Uploading to the mirror system</a></li>
+
+<li><a href='#mavencentral'>Uploading to maven repository</a></li>
+
+<li><a href='#announcing'>Announcing the release</a></li>
+
+<li><a href='#additional'>Additional tasks</a></li>
+</ul>
+
+<h2 id='release-14'>Releasing Apache Wicket 1.4.x</h2>
<h3 id='building_the_release'>Building the release</h3>
@@ -198,8 +214,8 @@
<p>NOTE: If you get an error while generating javadocs like the one that
follows, run a <code>mvn clean install</code> followed by a <code>mvn
javadoc:jar</code>, then re-run <code>release.sh</code>. Example of error:
<code>java.lang.ClassCastException:
com.sun.tools.javadoc.ClassDocImpl</code></p>
-
-<h2 id='releasing_apache_wicket_13x'>Releasing Apache Wicket 1.3.x</h2>
+<a name='release-1.3.x'> </a>
+<h2 id='release13'>Releasing Apache Wicket 1.3.x</h2>
<h3 id='building_the_release'>Building the release</h3>
@@ -251,7 +267,7 @@ com.sun.tools.javadoc.ClassDocImpl</code
<li>announce</li>
</ul>
-<h2 id='uploading_to_the_mirror_system'>Uploading to the mirror system</h2>
+<h2 id='mirrors'>Uploading to the mirror system</h2>
<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>
@@ -262,7 +278,7 @@ com.sun.tools.javadoc.ClassDocImpl</code
<p>It is a good idea to clean up older releases from
/www/www.apache.org/dist/wicket/</p>
-<h2 id='uploading_to_maven_repository'>Uploading to maven repository</h2>
+<h2 id='mavencentral'>Uploading to maven repository</h2>
<p>I haven’t got any really good way to put them in the maven mirrors.
The problem is that right now we override the meta xml files, so only the
latest version is listed. If we really should do this perfect we would modify
meta files like /org/apache/wicket/wicket/maven-metadata.xml and add the
version to it (as well as create the hashes again).</p>
@@ -274,28 +290,31 @@ com.sun.tools.javadoc.ClassDocImpl</code
</div>
<p>Further reading: README under
/www/people.apache.org/repo/m2-ibiblio-rsync-repository/</p>
-<h2 id='announce'>Announce</h2>
+<h2 id='announcing'>Announcing the release</h2>
-<p><strong>FIXME</strong> Announcing is easier with the new CMS in place.
Describe these steps. I have tagged all the pages i usually update with a
update-for-release tag, see here
http://cwiki.apache.org/confluence/label/WICKETxSITE/update-for-release</p>
+<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>
-<li>http://wicket.apache.org</li>
-
-<li>http://wicket.apache.org/getting-wicket.html</li>
+<li>Write an announcement in the _posts directory</li>
-<li>http://wicket.apache.org/news.html</li>
+<li>Restart jekyll to regenerate the pages: it will automatically generate the
correct links in the navigation menu, quickstart and downloads page. It will
update the doap.rdf file, atom.xml rss feed and index.html file so that it
contains your announcement.</li>
<li>Send email to: [email protected], [email protected],
[email protected], [email protected]</li>
<li>Misc. websites like javalobby, serverside, onjava etc.</li>
</ul>
-<h2 id='additional_tasks'>Additional tasks</h2>
+<h2 id='additional'>Additional tasks</h2>
<ul>
-<li />
-
-<li>upload the JavaDocs to the website at
http://wicket.apache.org/docs/wicket-x.y.z/ and point JavaDocs link to it</li>
+<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.</li>
</ul>
</div>
<div id="clearer"></div>
Modified: wicket/common/site/trunk/contribute/release.md
URL:
http://svn.apache.org/viewvc/wicket/common/site/trunk/contribute/release.md?rev=985015&r1=985014&r2=985015&view=diff
==============================================================================
--- wicket/common/site/trunk/contribute/release.md (original)
+++ wicket/common/site/trunk/contribute/release.md Thu Aug 12 22:19:47 2010
@@ -3,7 +3,16 @@ layout: default
title: Build a release
---
-## Releasing Apache Wicket 1.4.x ##
+## Contents ##
+
+* [Releasing Apache Wicket 1.4.x](#release-14)
+* [Releasing Apache Wicket 1.3.x](#release-13)
+* [Uploading to the mirror system](#mirrors)
+* [Uploading to maven repository](#mavencentral)
+* [Announcing the release](#announcing)
+* [Additional tasks](#additional)
+
+## Releasing Apache Wicket 1.4.x ## {#release-14}
### Building the release ###
@@ -39,7 +48,8 @@ run a `mvn clean install` followed by a
`release.sh`. Example of error: `java.lang.ClassCastException:
com.sun.tools.javadoc.ClassDocImpl`
-## Releasing Apache Wicket 1.3.x ##
+<a name="release-1.3.x"> </a>
+## Releasing Apache Wicket 1.3.x ## { #release13 }
### Building the release ###
@@ -70,7 +80,7 @@ find . -name "pom.xml" | xargs sed -i ""
* wait 24 hours for mirrors to pick them up
* announce
-## Uploading to the mirror system ##
+## Uploading to the mirror system ## {#mirrors}
{% highlight console %}
ssh people.apache.org
@@ -84,7 +94,7 @@ Apache guide to mirros: http://apache.or
It is a good idea to clean up older releases from
/www/www.apache.org/dist/wicket/
-## Uploading to maven repository ##
+## Uploading to maven repository ## {#mavencentral}
I haven't got any really good way to put them in the maven mirrors. The
problem is that right now we override the meta xml files, so only the latest
@@ -102,20 +112,32 @@ chmod -R g+w * /www/people.apache.org/re
Further reading: README under
/www/people.apache.org/repo/m2-ibiblio-rsync-repository/
-## Announce ##
+## Announcing the release ## {#announcing}
+
+Edit the \_config.yaml file. This file contains a site wide configuration
+section specific to Wicket:
-**FIXME** Announcing is easier with the new CMS in place. Describe these steps.
-I have tagged all the pages i usually update with a update-for-release tag,
-see here
-http://cwiki.apache.org/confluence/label/WICKETxSITE/update-for-release
-
-* http://wicket.apache.org
-* http://wicket.apache.org/getting-wicket.html
-* http://wicket.apache.org/news.html
+{% highlight yaml %}
+wicket:
+ version: 1.4.10
+ released: 2010-08-11
+ versions: [1.3.7, 1.3-SNAPSHOT, 1.4.9, 1.4.10, 1.4-SNAPSHOT, 1.5-M1,
1.5-SNAPSHOT]
+{% endhighlight %}
+
+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).
+
+* Write an announcement in the \_posts directory
+* Restart jekyll to regenerate the pages: it will automatically generate the
+ correct links in the navigation menu, quickstart and downloads page. It will
+ update the doap.rdf file, atom.xml rss feed and index.html file so that it
+ contains your announcement.
* Send email to: [email protected], [email protected],
[email protected], [email protected]
* Misc. websites like javalobby, serverside, onjava etc.
-## Additional tasks ##
+## Additional tasks ## { #additional }
-* <strike>add the release to http://wicket.apache.org/quickstart.html and set
it as default</strike>
-* upload the JavaDocs to the website at
http://wicket.apache.org/docs/wicket-x.y.z/ and point JavaDocs link to it
+* Commit the JavaDocs to
+
[https://svn.apache.org/repos/asf/wicket/common/site/apidocs/1.4](https://svn.apache.org/repos/asf/wicket/common/site/apidocs/1.4)
+ svnpubsub will push this directly to our website.
