geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r893032 [13/21] - in /websites/production/geronimo/content: GMOxPMGT/ cache/
Date Mon, 06 Jan 2014 18:52:27 GMT
Modified: websites/production/geronimo/content/GMOxPMGT/geronimo-component-release-process.html
==============================================================================
--- websites/production/geronimo/content/GMOxPMGT/geronimo-component-release-process.html (original)
+++ websites/production/geronimo/content/GMOxPMGT/geronimo-component-release-process.html Mon Jan  6 18:52:26 2014
@@ -94,30 +94,38 @@
 
       <div class="pagecontent">
         <div class="wiki-content">
-          <div class="wiki-content maincontent"><div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Change Policy</b><br clear="none">Everyone is encouraged to update this documentation with clarifications, use of newer maven tooling, etc. Only major changes inconsistent with the spirit of this process need to be discussed on the dev list.</td></tr></table></div>
+          <div class="wiki-content maincontent">    <div class="aui-message warning shadowed information-macro">
+                    <p class="title">Change Policy</p>
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            
+<p>Everyone is encouraged to update this documentation with clarifications, use of newer maven tooling, etc. Only major changes inconsistent with the spirit of this process need to be discussed on the dev list.</p>
+                    </div>
+    </div>
+
 
-<h3><a shape="rect" name="GeronimoComponentReleaseProcess-Procedure"></a>Procedure</h3>
+<h3 id="GeronimoComponentReleaseProcess-Procedure">Procedure</h3>
 
 <ol><li>Whenever possible, use the maven release plugin. If something doesn't work file a bug against it.</li><li>Use extreme caution in creating branches as opposed to releasing from trunk. While "core" geronimo may need to keep branches, most smaller projects such as specs, plugins, components, and most likely tools should avoid the complexity of branches unless clearly necessary and agreed upon.</li><li>When branches are needed, branches/x.y would be the branch for all x.y.z releases</li></ol>
 
 
 <p>The next sections are copied from <a shape="rect" class="external-link" href="http://maven.apache.org/developers/release/releasing.html">http://maven.apache.org/developers/release/releasing.html</a> with modifications for Geronimo.</p>
 
-<p><a shape="rect" name="GeronimoComponentReleaseProcess-releasing"></a></p>
-<h2><a shape="rect" name="GeronimoComponentReleaseProcess-ReleasingAGeronimoProject"></a>Releasing A Geronimo Project</h2>
+<p><span class="confluence-anchor-link" id="GeronimoComponentReleaseProcess-releasing"></span></p>
+<h2 id="GeronimoComponentReleaseProcess-ReleasingAGeronimoProject">Releasing A Geronimo Project</h2>
 
 <p>What follows is a description of releasing a Geronimo project to a staging repository, whereupon it is scrutinized by the community, approved, and transfered to a production repository.<br clear="none">
 Prerequisite</p>
 
 <p>Be sure that:</p>
 
-<ul><li>you have all Maven servers defined in your <tt>settings.xml</tt>. For more information, please refer to <a shape="rect" class="external-link" href="http://maven.apache.org/developers/committer-settings.html">Maven Committer settings</a> which also apply for Geronimo committers.</li><li>you have created your GPG keys. For more information, please refer to <a shape="rect" class="external-link" href="http://maven.apache.org/developers/release/pmc-gpg-keys.html">Making GPG Keys</a>.</li></ul>
+<ul><li>you have all Maven servers defined in your <code>settings.xml</code>. For more information, please refer to <a shape="rect" class="external-link" href="http://maven.apache.org/developers/committer-settings.html">Maven Committer settings</a> which also apply for Geronimo committers.</li><li>you have created your GPG keys. For more information, please refer to <a shape="rect" class="external-link" href="http://maven.apache.org/developers/release/pmc-gpg-keys.html">Making GPG Keys</a>.</li></ul>
 
 
-<p>In order to release a project you must also have the following setup in your <tt>$HOME/.m2/settings.xml</tt> which is a profile that defines the staging repository.</p>
+<p>In order to release a project you must also have the following setup in your <code>$HOME/.m2/settings.xml</code> which is a profile that defines the staging repository.</p>
 
-<p>Here's what your release profile might look like in your <tt>$HOME/.m2/settings.xml</tt> :</p>
-<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<p>Here's what your release profile might look like in your <code>$HOME/.m2/settings.xml</code> :</p>
+<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 &lt;settings&gt;
     &lt;profiles&gt;
@@ -160,8 +168,15 @@ Prerequisite</p>
 ]]></script>
 </div></div>
 
-<div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">The server name apache.releases at the start of deploy.altRepository must correspond to the apache.releases server definition.  <br clear="none">
-Also that your apache id does not start with "~".</td></tr></table></div>
+    <div class="aui-message warning shadowed information-macro">
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            
+<p>The server name apache.releases at the start of deploy.altRepository must correspond to the apache.releases server definition.  <br clear="none">
+Also that your apache id does not start with "~".</p>
+                    </div>
+    </div>
+
 
 <p>Everything that you need to release has (will have, actually) been configured in the genesis root pom all Geronimo projects inherit from. </p>
 
@@ -169,7 +184,7 @@ Also that your apache id does not start 
 
 <p>This is the base release configuration in the genesis root pom:</p>
 
-<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
         &lt;profile&gt;
             &lt;id&gt;release&lt;/id&gt;
@@ -251,11 +266,11 @@ Also that your apache id does not start 
 ]]></script>
 </div></div>
 
-<h2><a shape="rect" name="GeronimoComponentReleaseProcess-ReleaseProcessforPartOfGeronimo"></a>Release Process for Part Of Geronimo</h2>
+<h2 id="GeronimoComponentReleaseProcess-ReleaseProcessforPartOfGeronimo">Release Process for Part Of Geronimo</h2>
 
 <p>1. Prepare your poms for release:<br clear="none">
 Genesis and the recommended settings.xml file above rely on the existence of some configuration in the top level pom in your project to parameterize where in your staging area the release will be located.  This makes it so you can have multiple independent releases under vote in your staging area at once, and clearly locates the maven generated site in the documentation once the release is completed.  You should only need to do this the first time these instructions are used.</p>
-<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 &lt;properties&gt;
 &lt;!-- siteId locates the staging repo and staging site via the settings.xml profiles --&gt;
@@ -278,7 +293,7 @@ Genesis and the recommended settings.xml
 <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
 <pre>mvn release:prepare -Prelease -DdryRun=true
 </pre>
-</div></div></li><li>Diff the original file <tt>pom.xml</tt> with the one called <tt>pom.xml.tag</tt> to see if the license or any other info has been removed. This has been known to happen if the starting &lt;project&gt; tag is not on a single line. The only things that should be different between these files are the <tt>&lt;version&gt;</tt> and <tt>&lt;scm&gt;</tt> elements. Any other changes, you must back-port yourself to the original <tt>pom.xml</tt> file and commit before proceeding with the release.</li><li>Remember to do <tt>mvn release:clean</tt> before you start the real release process.<br clear="none">
+</div></div></li><li>Diff the original file <code>pom.xml</code> with the one called <code>pom.xml.tag</code> to see if the license or any other info has been removed. This has been known to happen if the starting &lt;project&gt; tag is not on a single line. The only things that should be different between these files are the <code>&lt;version&gt;</code> and <code>&lt;scm&gt;</code> elements. Any other changes, you must back-port yourself to the original <code>pom.xml</code> file and commit before proceeding with the release.</li><li>Remember to do <code>mvn release:clean</code> before you start the real release process.<br clear="none">
 2. (optional) Publish a snapshot:</li></ul>
 
 
@@ -291,17 +306,32 @@ Genesis and the recommended settings.xml
 </pre>
 </div></div>
 
-<div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Important</b><br clear="none">IMPORTANT NOTE: Be sure that the generated artifacts respect the Apache release rules : NOTICE and LICENSE files should be present in the META-INF directory within the jar. For -sources artifacts, be sure that your pom does NOT use the maven-source-plugin:2.0.3 which is broken. The recommended version at this time is 2.0.4.  All this should be automated <br clear="none">
-via the maven-remote-resources-plugin (installs legal files) and the tools-maven-plugin (checks for legal files).
+    <div class="aui-message warning shadowed information-macro">
+                    <p class="title">Important</p>
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            
+<p>IMPORTANT NOTE: Be sure that the generated artifacts respect the Apache release rules : NOTICE and LICENSE files should be present in the META-INF directory within the jar. For -sources artifacts, be sure that your pom does NOT use the maven-source-plugin:2.0.3 which is broken. The recommended version at this time is 2.0.4.  All this should be automated <br clear="none">
+via the maven-remote-resources-plugin (installs legal files) and the tools-maven-plugin (checks for legal files).</p>
+
+<p>If during mvn deploy command, you are challenged for password many times, you may want to create ssh private and public keys.</p>
+                    </div>
+    </div>
 
-<p>If during mvn deploy command, you are challenged for password many times, you may want to create ssh private and public keys.</p></td></tr></table></div>
 
-<div class="panelMacro"><table class="tipMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">You could verify the deployment under Apache Snapshot repository.
+    <div class="aui-message success shadowed information-macro">
+                            <span class="aui-icon icon-success">Icon</span>
+                <div class="message-content">
+                            
+<p>You could verify the deployment under Apache Snapshot repository.</p>
 
 <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
 <pre>http://people.apache.org/repo/m2-snapshot-repository/org/apache/geronimo/...
 </pre>
-</div></div></td></tr></table></div>
+</div></div>
+                    </div>
+    </div>
+
 
 <p>3. Prepare the release</p>
 
@@ -313,13 +343,21 @@ via the maven-remote-resources-plugin (i
 
 <p>Preparing the release will create the new tag in SVN, automatically checking in on your behalf.  </p>
 
-<div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>getting authorization failure</b><br clear="none">If the prepare release command failed because of authorization failure, like below:<br clear="none">
+    <div class="aui-message warning shadowed information-macro">
+                    <p class="title">getting authorization failure</p>
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            
+<p>If the prepare release command failed because of authorization failure, like below:<br clear="none">
 svn: MKACTIVITY of '/repos/asf/!svn/act/6ed2cc4d-dae9-4134-9cfb-f17cc8dd02ea': authorization failed (<a shape="rect" class="external-link" href="https://svn.apache.org">https://svn.apache.org</a>)<br clear="none">
-You can issue "mvn release:prepare -Prelease -Dusername=username -Dpassword=password" instead.</td></tr></table></div>
+You can issue "mvn release:prepare -Prelease -Dusername=username -Dpassword=password" instead.</p>
+                    </div>
+    </div>
+
 
 <p>4. Make a copy of the checked out project in this state in case you need to roll back the release</p>
 
-<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 cd ..
 cp -r trunk trunk-prepared
@@ -336,17 +374,31 @@ cd trunk
 </pre>
 </div></div>
 
-<div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">If the project lists the default modules in a profile you MUST include that profile and the release profile in the command line!  For instance if the default profile id is "default" the command line would be
+    <div class="aui-message warning shadowed information-macro">
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            
+<p>If the project lists the default modules in a profile you MUST include that profile and the release profile in the command line!  For instance if the default profile id is "default" the command line would be</p>
 <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
 <pre>mvn release:perform -Pdefault,release
 </pre>
-</div></div></td></tr></table></div>
+</div></div>
+                    </div>
+    </div>
+
 
 <p>6. Stage the latest documentation (if there is an actual maven generated site)</p>
 
-<div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">See the <a shape="rect" class="external-link" href="http://geronimo.apache.org/maven/genesis/1.4/config/project-config/index.html">genesis project-config</a> site page for instructions on how to set up your project so site staging works.<br clear="none">
+    <div class="aui-message warning shadowed information-macro">
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            
+<p>See the <a shape="rect" class="external-link" href="http://geronimo.apache.org/maven/genesis/1.4/config/project-config/index.html">genesis project-config</a> site page for instructions on how to set up your project so site staging works.<br clear="none">
 Note that the -Prelease profile is needed to specify the profile in settings.xml that configures the staging location.<br clear="none">
-Build the site from the tag that release:perform checked out into target/checkout in step 5.</td></tr></table></div>
+Build the site from the tag that release:perform checked out into target/checkout in step 5.</p>
+                    </div>
+    </div>
+
 
 <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
 <pre>cd target/checkout
@@ -396,7 +448,14 @@ Vote open for 72 hours.
 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>
 
 <p>Note: Current version of the stage plugin is 1.0-alpha-1. There's probably an easier way, but I added it to a pom and built to pull it down.</p>
-<div class="panelMacro"><table class="warningMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/forbidden.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">This version of the stage plugin does not work with maven 2.0.9.  Use a suitable path to maven so you run it using maven 2.0.8.  Note that the stage plugin does not use any info from the project so this should cause no problems</td></tr></table></div>
+    <div class="aui-message problem shadowed information-macro">
+                            <span class="aui-icon icon-problem">Icon</span>
+                <div class="message-content">
+                            
+<p>This version of the stage plugin does not work with maven 2.0.9.  Use a suitable path to maven so you run it using maven 2.0.8.  Note that the stage plugin does not use any info from the project so this should cause no problems</p>
+                    </div>
+    </div>
+
 <p>Here is an example on how to use the stage plugin:</p>
 
 <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
@@ -407,9 +466,22 @@ Once the release is deemed fit for publi
 </pre>
 </div></div>
 
-<div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">The version parameter is currently ignored and the entire staging repository is synced, not just the given version or the current project. It still needs to be provided, though.</td></tr></table></div>
+    <div class="aui-message warning shadowed information-macro">
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            
+<p>The version parameter is currently ignored and the entire staging repository is synced, not just the given version or the current project. It still needs to be provided, though.</p>
+                    </div>
+    </div>
+
+
+    <div class="aui-message warning shadowed information-macro">
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            <p>Ensure that your public PGP key is in appropriate public locations (esp. /www/www.apache.org/dist/geronimo/KEYS on people and <a shape="rect" class="external-link" href="http://pgp.mit.edu/" rel="nofollow">http://pgp.mit.edu/</a>) and that your pgp key has been signed by several other apache committers to create a web of trust.</p>
+                    </div>
+    </div>
 
-<div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">Ensure that your public PGP key is in appropriate public locations (esp. /www/www.apache.org/dist/geronimo/KEYS on people and <a shape="rect" class="external-link" href="http://pgp.mit.edu/" rel="nofollow">http://pgp.mit.edu/</a>) and that your pgp key has been signed by several other apache committers to create a web of trust.</td></tr></table></div>
 
 <p>9. Deploy the current and versioned websites (if there is a reasonable maven generated site)</p>
 
@@ -429,17 +501,17 @@ chmod -R g+w /www/geronimo.apache.org/ma
 <p><a shape="rect" class="external-link" href="http://geronimo.apache.org/">http://geronimo.apache.org/</a>...</p>
 
 <p>11. Update the plugins page<br clear="none">
-If this is a plugin release, update the apache <tt>geronimo-plugins.xml</tt>.<br clear="none">
+If this is a plugin release, update the apache <code>geronimo-plugins.xml</code>.<br clear="none">
 PROPOSAL ON HOW TO DO THIS:</p>
 
 <p>First, perform the release.  This process could be done as part of the release but that may be too confusing.  The important point is to build the new tag with a fresh copy of geronimo-plugins.xml.<br clear="none">
-The official <tt>geronimo-plugins.xml</tt> is located in svn under e.g. geronimo/site/trunk/docs/plugins/geronimo-2.1/geronimo-plugins.xml<br clear="none">
-copy this file to <tt>~/.m2/repository/geronimo-plugins.xml</tt><br clear="none">
-run <tt>mvn clean install</tt> on a fresh checkout of the new tag.<br clear="none">
+The official <code>geronimo-plugins.xml</code> is located in svn under e.g. geronimo/site/trunk/docs/plugins/geronimo-2.1/geronimo-plugins.xml<br clear="none">
+copy this file to <code>~/.m2/repository/geronimo-plugins.xml</code><br clear="none">
+run <code>mvn clean install</code> on a fresh checkout of the new tag.<br clear="none">
 copy the merged geronimo-plugins.xml back your svn site checkout.<br clear="none">
 Put the apache license header back in to the merged file (the car-maven-plugin removes it)<br clear="none">
 Edit the source-repository elements in the new plugins if necessary.  They should contain </p>
-<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
             &lt;source-repository&gt;http://repo1.maven.org/maven2/&lt;/source-repository&gt;
 ]]></script>
@@ -472,55 +544,70 @@ Enjoy,
 </pre>
 </div></div>
 
-<div class="panelMacro"><table class="warningMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/forbidden.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">we don't seem to have a "next board report" or a recent releases page in the wiki</td></tr></table></div>
+    <div class="aui-message problem shadowed information-macro">
+                            <span class="aui-icon icon-problem">Icon</span>
+                <div class="message-content">
+                            
+<p>we don't seem to have a "next board report" or a recent releases page in the wiki</p>
+                    </div>
+    </div>
+
 <p>14. Add the release to the next board report, in the private subversion area. <br clear="none">
 15. Add the release to the wiki, under the Recent Releases section of the front page and on the Releases page.<br clear="none">
 16. Celebrate :o)</p>
 
-<h3><a shape="rect" name="GeronimoComponentReleaseProcess-NotesandGotchas"></a>Notes and Gotchas</h3>
+<h3 id="GeronimoComponentReleaseProcess-NotesandGotchas">Notes and Gotchas</h3>
 <ul><li>If the selection of modules for the default build is set in a default profile then more work will be necessary.  When genesis did not have the modules specified in the base pom this involved running mvn release:perform -Pdefault,release which only deploys the root, then running mvn deploy -Prelease in each of the 3 modules listed in the default profile.  For projects that are not expected to be used as parents of independently releasable projects (for instance server/trunk) including the list of modules in the release profile override should work.  Better still is just having the modules outside a profile.</li></ul>
 
 
 
 
-<h2><a shape="rect" name="GeronimoComponentReleaseProcess-Whenusingthemavenreleasepluginisimpossible%28thisshouldbealessfrequenteventasweprogress%29%3A"></a>When using the maven release plugin is impossible (this should be a less frequent event as we progress):</h2>
-<ol><li>when a release is frozen, we spin off a branch with that <b>exact</b> name, as in branches/x.y.z, where z starts at zero and increments by one.</li><li>at that time branches/x.y is immediately updated to version x.y.(z+1)-SNAPSHOT</li><li>We cut releases from the frozen branch</li><li>When a release passes final tck testing and final vote, the frozen branch is moved to tags</li></ol>
+<h2 id="GeronimoComponentReleaseProcess-Whenusingthemavenreleasepluginisimpossible(thisshouldbealessfrequenteventasweprogress):">When using the maven release plugin is impossible (this should be a less frequent event as we progress):</h2>
+<ol><li>when a release is frozen, we spin off a branch with that <strong>exact</strong> name, as in branches/x.y.z, where z starts at zero and increments by one.</li><li>at that time branches/x.y is immediately updated to version x.y.(z+1)-SNAPSHOT</li><li>We cut releases from the frozen branch</li><li>When a release passes final tck testing and final vote, the frozen branch is moved to tags</li></ol>
 
 
-<h3><a shape="rect" name="GeronimoComponentReleaseProcess-Updatingthepomsaftermakinganewbranch"></a>Updating the poms after making a new branch</h3>
+<h3 id="GeronimoComponentReleaseProcess-Updatingthepomsaftermakinganewbranch">Updating the poms after making a new branch</h3>
 
 <p>Once a new branch is created you will generally need to manage the version number in the poms.  The following Perl scripts will assist in that task.  It could use some polishing but given the relatively infrequent use.</p>
 <div class="panel" style="border-style: solid;border-width: 1px;"><div class="panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>Pom Version Changer</b></div><div class="panelContent">
 <p>perl -i.orig -pe '<br clear="none">
  $done = 0 if /&lt;?xml/;<br clear="none">
  $inParent = 1 if not $done and /&lt;parent&gt;/;<br clear="none">
- s,<b><em>oldVersion</em></b>&lt;/version&gt;,<b><em>newVersion</em></b>&lt;/version&gt;, if $inParent and not $done;<br clear="none">
+ s,<strong><em>oldVersion</em></strong>&lt;/version&gt;,<strong><em>newVersion</em></strong>&lt;/version&gt;, if $inParent and not $done;<br clear="none">
  $done = $inParent = 1 if /&lt;\/parent&gt;/;<br clear="none">
- ' $(find <b><em>GeronimoDirectory</em></b> -name pom.xml | grep -v "<b><em>GeronimoDirectory</em></b>/pom.xml")</p>
+ ' $(find <strong><em>GeronimoDirectory</em></strong> -name pom.xml | grep -v "<strong><em>GeronimoDirectory</em></strong>/pom.xml")</p>
 </div></div>
-<p>Remember to properly escape periods in the <b><em>oldVersion</em></b>.  For instance, to change 1.1.1-SNAPSHOT to 1.1.1 you would have</p>
+<p>Remember to properly escape periods in the <strong><em>oldVersion</em></strong>.  For instance, to change 1.1.1-SNAPSHOT to 1.1.1 you would have</p>
 <div class="panel" style="border-style: solid;border-width: 1px;"><div class="panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>Example</b></div><div class="panelContent">
 <p>perl -i.orig -pe '<br clear="none">
  $done = 0 if /&lt;?xml/;<br clear="none">
  $inParent = 1 if not $done and /&lt;parent&gt;/;<br clear="none">
- s,<b><em>1\.1\.1-SNAPSHOT</em></b>&lt;/version&gt;,<b><em>1.1.1</em></b>&lt;/version&gt;, if $inParent and not $done;<br clear="none">
+ s,<strong><em>1\.1\.1-SNAPSHOT</em></strong>&lt;/version&gt;,<strong><em>1.1.1</em></strong>&lt;/version&gt;, if $inParent and not $done;<br clear="none">
  $done = $inParent = 1 if /&lt;\/parent&gt;/;<br clear="none">
- ' $(find <b><em>GeronimoDirectory</em></b> -name pom.xml | grep -v "<b><em>GeronimoDirectory</em></b>/pom.xml")</p>
+ ' $(find <strong><em>GeronimoDirectory</em></strong> -name pom.xml | grep -v "<strong><em>GeronimoDirectory</em></strong>/pom.xml")</p>
 </div></div>
 
-<div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>making the above script work</b><br clear="none">You must replace <b><em>GeronimoDirectory</em></b> above with the fully qualified path to the directory (using "~" will not work).<br clear="none">
-Also note:  There are references to versions outside of the pom parent entries updated by the script which will also need to be updated with the new version.</td></tr></table></div>
+    <div class="aui-message warning shadowed information-macro">
+                    <p class="title">making the above script work</p>
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            
+<p>You must replace <strong><em>GeronimoDirectory</em></strong> above with the fully qualified path to the directory (using "~" will not work).<br clear="none">
+Also note:  There are references to versions outside of the pom parent entries updated by the script which will also need to be updated with the new version.</p>
+                    </div>
+    </div>
+
 
-<h3><a shape="rect" name="GeronimoComponentReleaseProcess-Rationale"></a>Rationale</h3>
+<h3 id="GeronimoComponentReleaseProcess-Rationale">Rationale</h3>
 
 <p>We create a branch at freeze time for the following reasons:</p>
 <ol><li>it takes at least one week from freeze to ship due to voting, tck testing and potential repeats of that process (re-cut, re-certify, re-vote). There is no reason why work on x.y.z+1 needs to be delayed - only 52 weeks a year.</li><li>stronger guarantee no one is updating the branch once frozen</li><li>less likely that people and ci systems (continuum) will checkout and build pre-release versions of x.y.z (not x.y.z-SNAPSHOT) which would need to be removed manually and may accidentally be distributed.</li><li>it is currently very difficult to roll version numbers forward, entries here and there are often missed. Far better to have branches/x.y have a few straggling old x.y.z-SNAPSHOT versions than a few overlooked x.y.z final numbers that needed to go back to SNAPSHOT - they never leave SNAPSHOT and need to be reverted back later if that process happens in the frozen branch.</li></ol>
 
 
-<h3><a shape="rect" name="GeronimoComponentReleaseProcess-Steps"></a>Steps</h3>
+<h3 id="GeronimoComponentReleaseProcess-Steps">Steps</h3>
 
-<ol><li>Download and install the Gnu Privacy Guard (GPG) from <a shape="rect" class="external-link" href="http://www.gnupg.org" rel="nofollow">http://www.gnupg.org</a>. Read the documentation on that site and create a key. Have the key signed and verified by others. Submit your public key to <a shape="rect" class="external-link" href="http://pgp.mit.edu/" rel="nofollow">http://pgp.mit.edu/</a>. This is a one time process.</li><li>Create a "staging" profile in your <tt>~/.m2/settings.xml</tt>
-<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<ol><li>Download and install the Gnu Privacy Guard (GPG) from <a shape="rect" class="external-link" href="http://www.gnupg.org" rel="nofollow">http://www.gnupg.org</a>. Read the documentation on that site and create a key. Have the key signed and verified by others. Submit your public key to <a shape="rect" class="external-link" href="http://pgp.mit.edu/" rel="nofollow">http://pgp.mit.edu/</a>. This is a one time process.</li><li>Create a "staging" profile in your <code>~/.m2/settings.xml</code>
+<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 &lt;profile&gt;
     &lt;id&gt;staging&lt;/id&gt;
@@ -535,8 +622,8 @@ Also note:  There are references to vers
 <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
 <pre>svn mv SRC-URL DEST-URL -m "Reason for this commit".
 </pre>
-</div></div></li><li>Checkout or update this branches tree on your machine.</li><li>Update the &lt;scm&gt; urls in the <tt>pom.xml</tt> to point to the final url in tags. Eg:
-<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+</div></div></li><li>Checkout or update this branches tree on your machine.</li><li>Update the &lt;scm&gt; urls in the <code>pom.xml</code> to point to the final url in tags. Eg:
+<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 &lt;scm&gt;
      &lt;connection&gt;scm:svn:http://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-servlet_2.5_spec-1.1&lt;/connection&gt;
@@ -552,19 +639,41 @@ Others -
     mvn -pdefault,staging deploy
 </pre>
 </div></div>
-<div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Staging</b><br clear="none">Before running this step, verify that there is a corresponding "staging" or "release" profile in pom.xml.  Some of the newer releases, will require you to use -Pdefault,release as we are trying to make it impossible to directly release artifacts to the apache.release repo by providing a default "release" profile that stages files to public people.apache.org directory.</td></tr></table></div></li><li>Go the temporary staging directory specified by <tt>deploy.altRepository</tt> element in the <em>staging</em> profile of your <tt>settings.xml</tt>. Delete all *.asc.* files under this directory tree. Tar the staging directory us
 ing the command
+    <div class="aui-message warning shadowed information-macro">
+                    <p class="title">Staging</p>
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            
+<p>Before running this step, verify that there is a corresponding "staging" or "release" profile in pom.xml.  Some of the newer releases, will require you to use -Pdefault,release as we are trying to make it impossible to directly release artifacts to the apache.release repo by providing a default "release" profile that stages files to public people.apache.org directory.</p>
+                    </div>
+    </div>
+</li><li>Go the temporary staging directory specified by <code>deploy.altRepository</code> element in the <em>staging</em> profile of your <code>settings.xml</code>. Delete all *.asc.* files under this directory tree. Tar the staging directory using the command
 <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
 <pre>find . -name *.asc.* | xargs rm -f
 tar -zcvf release.tar.gz releases
 </pre>
 </div></div>
-<div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">Ensure you include the *.asc files, as these are required and will be checked for by the Apache Repository team.</td></tr></table></div></li><li>Copy the tar ball to a publicly accessible location. Put it for a vote. In the vote notice, please include the precise names and versions being voted on (e.g. geronimo-javamail_1.4_spec-1.1) and the svn urls to the current source and where the tag will be created.</li><li>After it has been approved, untar the tar ball into the appropriate maven structure on people.apache.org under the directory /www/people.apache.org/repo/m2-ibiblio-rsync-repository. A cron job will rsync this with ibiblio and release it into
  the wild.
+    <div class="aui-message hint shadowed information-macro">
+                            <span class="aui-icon icon-hint">Icon</span>
+                <div class="message-content">
+                            
+<p>Ensure you include the *.asc files, as these are required and will be checked for by the Apache Repository team.</p>
+                    </div>
+    </div>
+</li><li>Copy the tar ball to a publicly accessible location. Put it for a vote. In the vote notice, please include the precise names and versions being voted on (e.g. geronimo-javamail_1.4_spec-1.1) and the svn urls to the current source and where the tag will be created.</li><li>After it has been approved, untar the tar ball into the appropriate maven structure on people.apache.org under the directory /www/people.apache.org/repo/m2-ibiblio-rsync-repository. A cron job will rsync this with ibiblio and release it into the wild.
 <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
 <pre>gunzip foo.tar.gz
 tar -xvf foo.tar
 </pre>
 </div></div>
-<div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">Ensure that the files you copy to the rsync directory have <tt>0775</tt> dir permission and a <tt>0664</tt> file permission set on them.</td></tr></table></div></li><li>Move the branches to tags using the following command.
+    <div class="aui-message hint shadowed information-macro">
+                            <span class="aui-icon icon-hint">Icon</span>
+                <div class="message-content">
+                            
+<p>Ensure that the files you copy to the rsync directory have <code>0775</code> dir permission and a <code>0664</code> file permission set on them.</p>
+                    </div>
+    </div>
+</li><li>Move the branches to tags using the following command.
 <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
 <pre>svn mv SRC-URL DEST-URL -m "Reason for this commit".
 </pre>
@@ -572,7 +681,7 @@ tar -xvf foo.tar
 
 
 
-<h3><a shape="rect" name="GeronimoComponentReleaseProcess-Notice"></a>Notice</h3>
+<h3 id="GeronimoComponentReleaseProcess-Notice">Notice</h3>
 
 <p>The original process in this document was voted on by the Geronimo community. Please formally propose all changes to dev@geronimo.apache.org.</p>
 
@@ -582,8 +691,7 @@ tar -xvf foo.tar
 
 <p>Revised process using maven tools voted on in March 2008.  Only major structural changes now require votes.</p>
 
-<p>See: (not yet in archive)</p>
-</div>
+<p>See: (not yet in archive)</p></div>
         </div>
 
         

Modified: websites/production/geronimo/content/GMOxPMGT/geronimo-eclipse-plugin-release-process.html
==============================================================================
--- websites/production/geronimo/content/GMOxPMGT/geronimo-eclipse-plugin-release-process.html (original)
+++ websites/production/geronimo/content/GMOxPMGT/geronimo-eclipse-plugin-release-process.html Mon Jan  6 18:52:26 2014
@@ -84,74 +84,115 @@
 
       <div class="pagecontent">
         <div class="wiki-content">
-          <div class="wiki-content maincontent"><h3><a shape="rect" name="GeronimoEclipsePluginReleaseProcess-Steps"></a>Steps</h3>
+          <div class="wiki-content maincontent"><h3 id="GeronimoEclipsePluginReleaseProcess-Steps">Steps</h3>
 
 <p>&#160;&#160; &#160; &#160;Before starting the process, make sure these work below has been done:</p>
 
 <ul><li>All version numbers in GEP are correct for issuing "mvn release:prepare", including plugin version in MANIFEST.MF</li><li>Assure all the dependency version number is synchronized with Geronimo server</li><li>With tool Apache RAT, scan all the source code to make sure Apache license headers have been added into neccessarily. The header is neccessary for .java, .xsd,.xml,.html and .properties, which contain functional code or configuration information.</li></ul>
 
 
-<ol><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> The plan is to sync Geronimo Eclipse Plugin (GEP) releases with those of the Geronimo server. The goal is to release GEP as soon as possible after the release of the corresponding server.&#160;
+<ol><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> The plan is to sync Geronimo Eclipse Plugin (GEP) releases with those of the Geronimo server. The goal is to release GEP as soon as possible after the release of the corresponding server.&#160;
 <br clear="none" class="atl-forced-newline">
-<div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Note:</b> These notes are written for release 2.2.  Change the version number accordingly for your release!</td></tr></table></div>
-<p><br clear="none" class="atl-forced-newline"></p></li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Pick up JIRA list of fixed bugs and new features from <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa">Release Notes</a> and defer unresolved JIRAs</li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Update the release notes.  They are the file PLUGIN_RELEASE-NOTES-2.2.txt in trunk. Copy the JIRA list from Step 2 into it.&#160;</li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Remove snapshot from version number of dependency. Eg. geronimo-kernel-2.2-SNAPSHOT.jar in MANIFEST.MF of runtime.v22.&#160;</li><
 li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Build the new <b>branches</b> tree that will soon be released</li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Ensure that your GPG public key is in the /www/www.apache.org/dist/geronimo/KEYS file and KEYS in svn server before publishing anything to the distribution location</li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Prepare the release with maven release plugin. Refer to <a shape="rect" class="external-link" href="http://maven.apache.org/developers/release/apache-release.html">http://maven.apache.org/developers/release/apache-release.html</a>
+    <div class="aui-message warning shadowed information-macro">
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            
+<p><strong>Note:</strong> These notes are written for release 2.2.  Change the version number accordingly for your release!</p>
+                    </div>
+    </div>
+
+<br clear="none" class="atl-forced-newline"></li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Pick up JIRA list of fixed bugs and new features from <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa">Release Notes</a> and defer unresolved JIRAs</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Update the release notes.  They are the file PLUGIN_RELEASE-NOTES-2.2.txt in trunk. Copy the JIRA list from Step 2 into it.&#160;</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/
 emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Remove snapshot from version number of dependency. Eg. geronimo-kernel-2.2-SNAPSHOT.jar in MANIFEST.MF of runtime.v22.&#160;</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Build the new <strong>branches</strong> tree that will soon be released</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Ensure that your GPG public key is in the /www/www.apache.org/dist/geronimo/KEYS file and KEYS in svn server before publishing anything to the distribution location</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30
 bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Prepare the release with maven release plugin. Refer to <a shape="rect" class="external-link" href="http://maven.apache.org/developers/release/apache-release.html">http://maven.apache.org/developers/release/apache-release.html</a>
 	<ol><li>mvn release:prepare -Pallsubproject</li><li>mvn release:perform -Pallsubproject
 <br clear="none" class="atl-forced-newline">
-<div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Note:</b> Profile allsubproject is added since GEP 2.1.7 and 2.2.1 to include testsuite module during release but exclude the testsuite execution</td></tr></table></div>
-<p><br clear="none" class="atl-forced-newline"></p></li></ol>
-	</li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Set up a staging site for verifying update site at people.apache.org. Eg. &#160;<a shape="rect" class="external-link" href="http://people.apache.org/builds/geronimo/eclipse/updates/">http://people.apache.org/builds/geronimo/eclipse/updates/</a>, this staging site locates on people.apache.org here
+    <div class="aui-message warning shadowed information-macro">
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            
+<p><strong>Note:</strong> Profile allsubproject is added since GEP 2.1.7 and 2.2.1 to include testsuite module during release but exclude the testsuite execution</p>
+                    </div>
+    </div>
+
+<br clear="none" class="atl-forced-newline"></li></ol>
+	</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Set up a staging site for verifying update site at people.apache.org. Eg. &#160;<a shape="rect" class="external-link" href="http://people.apache.org/builds/geronimo/eclipse/updates/">http://people.apache.org/builds/geronimo/eclipse/updates/</a>, this staging site locates on people.apache.org here
 <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
 <pre>www/people.apache.org/builds/geronimo/eclipse/updates
 </pre>
 </div></div>
 	<ol><li>Extract geronimo-eclipse-plugin-2.2-updatesite.zip and calculate check sum for each files</li><li>Upload all the files into update site</li><li>Upload deployable.zip and updatesite.zip in a version sub directory, such as www/people.apache.org/builds/geronimo/eclipse/2.2.1</li></ol>
-	</li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Test the staging site by downloading the adapter from it</li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Create the How to install GEP v2.2 wiki page. Be sure this includes the pre-reqs. The idea is to have a single page with this release-specific information. In the vote note below, refer to this page, with overrides for the staging site URL. The idea here is to create the install page before hand, and use it for the voting, so that folks will review the doc we'll go live with when the vote passes. There is a How to install GEP page, with children of the various versions. These are for folks who may want to install old versions. When the vote passes, move all it's children to the v2.2 page, then rename the Ho
 w to install GEP page to the v2.2.1 page. Make it a child of the v2.1.2 page. Then, rename the v2.1.2 page to the generic How to install GEP page.</li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Close the staging repository in maven staging site in <a shape="rect" class="external-link" href="https://repository.apache.org/index.html#welcome">Sonatype Nexus Maven Repository Manager</a> so people reviewing the vote can see your artifacts.</li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Make sure to start a <b>[VOTE]</b> thread on the Geronimo dev list. In the vote notice, please include:
-	<ul class="alternate" type="square"><li>The precise names and versions being voted on (e.g. geronimo-eclipse-plugin-2.2-deployable.zip and geronimo-eclipse-plugin-2.2-updatesite.zip)
-<div class="panelMacro"><table class="tipMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Tips</b><br clear="none">1. Be certain to use the Release Candidate (RC) acronym in the name as it will not likely pass on the first vote<br clear="none">
-2. Be certain to use the same version numbers as the Geronimo Server (e.g., 2.2)</td></tr></table></div></li><li>URL of the staging site (with instructions on how to use it)</li><li>Eclipse requirements if any (with instructions on how to download them and from where)
+	</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Test the staging site by downloading the adapter from it</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Create the How to install GEP v2.2 wiki page. Be sure this includes the pre-reqs. The idea is to have a single page with this release-specific information. In the vote note below, refer to this page, with overrides for the staging site URL. The idea here is to create the install page before hand, and use it for the voting, so that folks will review the doc we'll go live with when the vote passes. There is a How to install GEP page, with children of the various versions. These a
 re for folks who may want to install old versions. When the vote passes, move all it's children to the v2.2 page, then rename the How to install GEP page to the v2.2.1 page. Make it a child of the v2.1.2 page. Then, rename the v2.1.2 page to the generic How to install GEP page.</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Close the staging repository in maven staging site in <a shape="rect" class="external-link" href="https://repository.apache.org/index.html#welcome">Sonatype Nexus Maven Repository Manager</a> so people reviewing the vote can see your artifacts.</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Make sure to star
 t a <strong>[VOTE]</strong> thread on the Geronimo dev list. In the vote notice, please include:
+	<ul class="alternate"><li>The precise names and versions being voted on (e.g. geronimo-eclipse-plugin-2.2-deployable.zip and geronimo-eclipse-plugin-2.2-updatesite.zip)
+    <div class="aui-message success shadowed information-macro">
+                    <p class="title">Tips</p>
+                            <span class="aui-icon icon-success">Icon</span>
+                <div class="message-content">
+                            <p>1. Be certain to use the Release Candidate (RC) acronym in the name as it will not likely pass on the first vote<br clear="none">
+2. Be certain to use the same version numbers as the Geronimo Server (e.g., 2.2)</p>
+                    </div>
+    </div>
+</li><li>URL of the staging site (with instructions on how to use it)</li><li>Eclipse requirements if any (with instructions on how to download them and from where)
 <br clear="none" class="atl-forced-newline">
 <br clear="none" class="atl-forced-newline">
-<div class="panelMacro"><table class="tipMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Tip</b><br clear="none">Be certain to get enough binding votes according to the Apache Foundation requirements, which in general stipulates 3 PMC +1 votes (see <a shape="rect" class="external-link" href="http://www.apache.org/foundation/voting.html#ReleaseVotes">http://www.apache.org/foundation/voting.html#ReleaseVotes</a> for more details)</td></tr></table></div></li></ul>
-	</li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> After the vote has been approved:
-	<ul class="alternate" type="square"><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Publish the results on a <b>[RESULTS]</b> reply to the original <b>[VOTE]</b> thread on the Geronimo dev list</li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Promote artifacts in maven staging site. You may find them on&#160;<a shape="rect" class="external-link" href="http://repository.apache.org/">http://repository.apache.org/</a> (The artifacts are promoted immediately.)</li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Publish the staging site, including the deployable.zip and updatesite.zip files, and the release notes to the <b>Geronimo Eclipse distribution</b> loc
 ation on people.apache.org here:
+    <div class="aui-message success shadowed information-macro">
+                    <p class="title">Tip</p>
+                            <span class="aui-icon icon-success">Icon</span>
+                <div class="message-content">
+                            <p>Be certain to get enough binding votes according to the Apache Foundation requirements, which in general stipulates 3 PMC +1 votes (see <a shape="rect" class="external-link" href="http://www.apache.org/foundation/voting.html#ReleaseVotes">http://www.apache.org/foundation/voting.html#ReleaseVotes</a> for more details)</p>
+                    </div>
+    </div>
+</li></ul>
+	</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> After the vote has been approved:
+	<ul class="alternate"><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Publish the results on a <strong>[RESULTS]</strong> reply to the original <strong>[VOTE]</strong> thread on the Geronimo dev list</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Promote artifacts in maven staging site. You may find them on&#160;<a shape="rect" class="external-link" href="http://repository.apache.org/">http://repository.apache.org/</a> (The artifacts are promoted immediately.)</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emotico
 ns/check.png" data-emoticon-name="tick" alt="(tick)"> Publish the staging site, including the deployable.zip and updatesite.zip files, and the release notes to the <strong>Geronimo Eclipse distribution</strong> location on people.apache.org here:
 <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
 <pre>/www/www.apache.org/dist/geronimo/eclipse
 </pre>
-</div></div></li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Ensure that the version subdirectory is used (e.g., 2.1.2)</li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Ensure that the file(s) you copy to the distribution directory have 0775 dir permission and a 0644 file permission set on them</li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Ensure that the file(s) you copy to the distribution directory have the RCx acronym removed from the filename
+</div></div></li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Ensure that the version subdirectory is used (e.g., 2.1.2)</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Ensure that the file(s) you copy to the distribution directory have 0775 dir permission and a 0644 file permission set on them</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Ensure that the file(s) you copy to the distribution directory have the RCx acronym removed from the filename
 <br clear="none" class="atl-forced-newline">
 <br clear="none" class="atl-forced-newline"></li></ul>
-	</li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Ensure that the corresponding <a shape="rect" class="external-link" href="http://apache.org/dist/geronimo/eclipse/"><b>Geronimo Eclipse distribution</b></a> website is updated automatically in the next 24 hours and properly with the deployable.zip file and the updatesite.zip file
+	</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Ensure that the corresponding <a shape="rect" class="external-link" href="http://apache.org/dist/geronimo/eclipse/"><strong>Geronimo Eclipse distribution</strong></a> website is updated automatically in the next 24 hours and properly with the deployable.zip file and the updatesite.zip file
 <br clear="none" class="atl-forced-newline">
-<br clear="none" class="atl-forced-newline"></li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Ensure that the file(s) you copy have the proper checksum files as well (i.e., .asc, .md5, .sha) using these gpg commands:
+<br clear="none" class="atl-forced-newline"></li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Ensure that the file(s) you copy have the proper checksum files as well (i.e., .asc, .md5, .sha) using these gpg commands:
 <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
 <pre>gpg --print-md MD5 [fileName] &gt; [fileName].md5
 gpg --print-md SHA1 [fileName] &gt; [fileName].sha
 gpg --armor --output [fileName].asc --detach-sig [fileName]
 </pre>
 </div></div>
-<p>NOTE: To generate keys, you need to notice the rules here <a shape="rect" class="external-link" href="http://www.apache.org/dev/openpgp.html#sha1">http://www.apache.org/dev/openpgp.html</a>and <a shape="rect" class="external-link" href="http://www.apache.org/dev/key-transition.html">http://www.apache.org/dev/key-transition.html</a><br clear="none">
-NOTE: Maven release plugin will generate the signature and checksum for all jar files, but for other files, you need to generate them manually.</p></li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Update the <b>Geronimo Eclipse Update Site</b> with the contents of the updatesite.zip:
+NOTE: To generate keys, you need to notice the rules here <a shape="rect" class="external-link" href="http://www.apache.org/dev/openpgp.html#sha1">http://www.apache.org/dev/openpgp.html</a>and <a shape="rect" class="external-link" href="http://www.apache.org/dev/key-transition.html">http://www.apache.org/dev/key-transition.html</a><br clear="none">
+NOTE: Maven release plugin will generate the signature and checksum for all jar files, but for other files, you need to generate them manually.</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Update the <strong>Geronimo Eclipse Update Site</strong> with the contents of the updatesite.zip:
 	<ol><li><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
 <pre>1. /www/www.apache.org/dist/geronimo/eclipse/updates/features
 2. /www/www.apache.org/dist/geronimo/eclipse/updates/plugins
 3. /www/www.apache.org/dist/geronimo/eclipse/updates/site.xml
 </pre>
 </div></div>
-<div class="panelMacro"><table class="warningMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/forbidden.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Warning</b><br clear="none">Never delete old releases from the update site - always append to it !! Likewise, do not create a new update site as this will break everyone who has this current site configured, and WTP which uses the update site for the downloadable server adapter support.</td></tr></table></div>
-<div class="panelMacro"><table class="warningMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/forbidden.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Warning</b><br clear="none">If you use FTP to transfer the files to the *Geronimo Eclipse Update Site&#160;*make sure to transfer everything in binary mode. Otherwise, the checksum files may not transfer correctly (especially if they are transferred in text mode).</td></tr></table></div></li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Ensure that the file(s) you copy to the update site directories have 0755 dir permission and a 0644 file permisison set on them</li></ol>
-	</li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Ensure that corresponding <a shape="rect" class="external-link" href="http://apache.org/dist/geronimo/eclipse/updates/"><b>Geronimo Eclipse Update Site</b></a> website (<a shape="rect" class="external-link" href="http://apache.org/dist/geronimo/eclipse/updates/">http://apache.org/dist/geronimo/eclipse/updates/</a>) is updated automatically in the next 24 hours with the contents of the updatesite.zip file.
-<br clear="none" class="atl-forced-newline"></li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Update the <a shape="rect" class="external-link" href="http://geronimo.apache.org/development-tools.html">Apache Geronimo Development Tools Subproject web site</a>. Please include:
-	<ul class="alternate" type="square"><li>Updated Release Notes</li><li>All Eclipse and WTP prerequisites and download instructions</li><li>Links to recent, pertinent, and relevant presentations (e.g., Shiva's, EclipseWorld, look for others, etc)
+    <div class="aui-message problem shadowed information-macro">
+                    <p class="title">Warning</p>
+                            <span class="aui-icon icon-problem">Icon</span>
+                <div class="message-content">
+                            <p>Never delete old releases from the update site - always append to it !! Likewise, do not create a new update site as this will break everyone who has this current site configured, and WTP which uses the update site for the downloadable server adapter support.</p>
+                    </div>
+    </div>
+
+    <div class="aui-message problem shadowed information-macro">
+                    <p class="title">Warning</p>
+                            <span class="aui-icon icon-problem">Icon</span>
+                <div class="message-content">
+                            <p>If you use FTP to transfer the files to the *Geronimo Eclipse Update Site&#160;*make sure to transfer everything in binary mode. Otherwise, the checksum files may not transfer correctly (especially if they are transferred in text mode).</p>
+                    </div>
+    </div>
+</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Ensure that the file(s) you copy to the update site directories have 0755 dir permission and a 0644 file permisison set on them</li></ol>
+	</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Ensure that corresponding <a shape="rect" class="external-link" href="http://apache.org/dist/geronimo/eclipse/updates/"><strong>Geronimo Eclipse Update Site</strong></a> website (<a shape="rect" class="external-link" href="http://apache.org/dist/geronimo/eclipse/updates/">http://apache.org/dist/geronimo/eclipse/updates/</a>) is updated automatically in the next 24 hours with the contents of the updatesite.zip file.
+<br clear="none" class="atl-forced-newline"></li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Update the <a shape="rect" class="external-link" href="http://geronimo.apache.org/development-tools.html">Apache Geronimo Development Tools Subproject web site</a>. Please include:
+	<ul class="alternate"><li>Updated Release Notes</li><li>All Eclipse and WTP prerequisites and download instructions</li><li>Links to recent, pertinent, and relevant presentations (e.g., Shiva's, EclipseWorld, look for others, etc)
 <br clear="none" class="atl-forced-newline">
 <br clear="none" class="atl-forced-newline"></li></ul>
-	</li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Administer the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/GERONIMODEVTOOLS">GERONIMODEVTOOLS JIRA project</a> to update the released and unreleased versions. Remember to mark the version as released.
+	</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Administer the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/GERONIMODEVTOOLS">GERONIMODEVTOOLS JIRA project</a> to update the released and unreleased versions. Remember to mark the version as released.
 <br clear="none" class="atl-forced-newline">
-<br clear="none" class="atl-forced-newline"></li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Update the <a shape="rect" class="external-link" href="http://geronimo.apache.org">Geronimo Home Page</a> with a News item that we have an updated Geronimo Eclipse Plugin available. Announce the availability in user@geronimo.apache.org, dev@geronimo.apache.org and&#160;<a shape="rect" class="external-link" href="mailto:announce@apache.org" rel="nofollow">announce@apache.org</a>.
+<br clear="none" class="atl-forced-newline"></li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Update the <a shape="rect" class="external-link" href="http://geronimo.apache.org">Geronimo Home Page</a> with a News item that we have an updated Geronimo Eclipse Plugin available. Announce the availability in user@geronimo.apache.org, dev@geronimo.apache.org and&#160;<a shape="rect" class="external-link" href="mailto:announce@apache.org" rel="nofollow">announce@apache.org</a>.
 <br clear="none" class="atl-forced-newline">
-<br clear="none" class="atl-forced-newline"></li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Final step is to update the <a shape="rect" class="external-link" href="http://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Release+Roadmaps">Geronimo Release Roadmaps</a> with the release date.</li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Update the version number of dependency and devtools in trunk for next release version. Begin the development of next release.
-	<ol><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Rename PLUGIN_RELEASE-NOTES-2.1.2.txt to PLUGIN_RELEASE-NOTES-2.1.3.txt.</li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Update version in plugin.xml from 2.1.2 to 2.1.3</li><li><img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif" height="16" width="16" alt="" border="0"> Update version in MANIFEST.MF from 2.1.2 to 2.1.3</li></ol>
-	</li></ol>
-</div>
+<br clear="none" class="atl-forced-newline"></li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Final step is to update the <a shape="rect" class="external-link" href="http://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Release+Roadmaps">Geronimo Release Roadmaps</a> with the release date.</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Update the version number of dependency and devtools in trunk for next release version. Begin the development of next release.
+	<ol><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Rename PLUGIN_RELEASE-NOTES-2.1.2.txt to PLUGIN_RELEASE-NOTES-2.1.3.txt.</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Update version in plugin.xml from 2.1.2 to 2.1.3</li><li><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"> Update version in MANIFEST.MF from 2.1.2 to 2.1.3</li></ol>
+	</li></ol></div>
         </div>
 
         

Modified: websites/production/geronimo/content/GMOxPMGT/geronimo-futures.html
==============================================================================
--- websites/production/geronimo/content/GMOxPMGT/geronimo-futures.html (original)
+++ websites/production/geronimo/content/GMOxPMGT/geronimo-futures.html Mon Jan  6 18:52:26 2014
@@ -86,12 +86,12 @@
         <div class="wiki-content">
           <div class="wiki-content maincontent"><p>The Geronimo Community is working on the following features for future releases:</p>
 
-<h2><a shape="rect" name="GeronimoFutures-JSRs"></a>JSRs</h2>
+<h2 id="GeronimoFutures-JSRs">JSRs</h2>
 <p>The Geronimo Community has members on the following JSRs expert groups:</p>
 <ul><li><a shape="rect" class="external-link" href="http://jcp.org/en/jsr/detail?id=236" rel="nofollow">JSR 236 Concurrency Utilities for Java EE</a> - Jarek Gawor</li><li><a shape="rect" class="external-link" href="http://jcp.org/en/jsr/detail?id=318" rel="nofollow">JSR 318 Enterprise JavaBeans 3.1</a> - David Blevins</li></ul>
 
 
-<h2><a shape="rect" name="GeronimoFutures-Investigation"></a>Investigation</h2>
+<h2 id="GeronimoFutures-Investigation">Investigation</h2>
 <p>We're also looking into the following areas:</p>
 <ul><li>Jetty v7/Servlet 3.0 - David Jencks - Support for Jetty v7 in Geronimo.</li><li>JSR-196 JASPI - David Jencks - Support for JASPI in Geronimo.</li><li>OSGi - Rick McGuire</li><li>Apache Tuscany</li><li>NetBeans IDE 6.5 support - Jacek Laskowski</li></ul>
 



Mime
View raw message