geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r893032 [16/21] - in /websites/production/geronimo/content: GMOxPMGT/ cache/
Date Mon, 06 Jan 2014 18:52:27 GMT
Modified: websites/production/geronimo/content/GMOxPMGT/geronimo-server-release-process.html
==============================================================================
--- websites/production/geronimo/content/GMOxPMGT/geronimo-server-release-process.html (original)
+++ websites/production/geronimo/content/GMOxPMGT/geronimo-server-release-process.html Mon
Jan  6 18:52:26 2014
@@ -94,28 +94,28 @@
 
       <div class="pagecontent">
         <div class="wiki-content">
-          <div class="wiki-content maincontent"><h3><a shape="rect" name="GeronimoServerReleaseProcess-Procedure"></a>Procedure</h3>
+          <div class="wiki-content maincontent"><h3 id="GeronimoServerReleaseProcess-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="GeronimoServerReleaseProcess-staging"></a></p>
+<p><span class="confluence-anchor-link" id="GeronimoServerReleaseProcess-staging"></span></p>
 
-<h2><a shape="rect" name="GeronimoServerReleaseProcess-ReleasingaGeronimoProject"></a>Releasing
a Geronimo Project</h2>
+<h2 id="GeronimoServerReleaseProcess-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;
@@ -157,14 +157,21 @@ Prerequisite</p>
 &lt;/settings&gt;
 ]]></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>
 
 <p>Your project should adhere to standard trunk,branches,tags svn layout in which case
no further release profile configuration should be needed.  Some slight deviation such as
our specs project still works without extra configuration.  Avoid more complex layouts that
require special configuration.</p>
 
 <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;
@@ -246,35 +253,43 @@ Also that your apache id does not start 
 ]]></script>
 </div></div>
 
-<h2><a shape="rect" name="GeronimoServerReleaseProcess-ReleaseProcessasusedforGeronimo2.1.x%3A"></a>Release
Process as used for Geronimo 2.1.x:</h2>
+<h2 id="GeronimoServerReleaseProcess-ReleaseProcessasusedforGeronimo2.1.x:">Release
Process as used for Geronimo 2.1.x:</h2>
 
 <p>This incorporates some aspects of the maven release process but stops short of actually
using the maven release plugin.  It utilizes a branch for the release process.</p>
-<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>
+<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="GeronimoServerReleaseProcess-Updatingthepomsaftermakinganewbranch"></a>Updating
the poms after making a new branch</h3>
+<h3 id="GeronimoServerReleaseProcess-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 for parent entries.  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>2\.1\.2-SNAPSHOT</em></b>&lt;/version&gt;,<b><em>2.1.2</em></b>&lt;/version&gt;,
if $inParent and not $done;<br clear="none">
+ s,<strong><em>2\.1\.2-SNAPSHOT</em></strong>&lt;/version&gt;,<strong><em>2.1.2</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>
-<p>In addition to the pom version changes there are several other places where version
updates are necessary.  To be certain all have been updated you should <b>grep</b>
the source for old version references to ensure that those remaining are correct.  Here is
an attempt to capture other version changes necessary:</p>
+    <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>
+
+<p>In addition to the pom version changes there are several other places where version
updates are necessary.  To be certain all have been updated you should <strong>grep</strong>
the source for old version references to ensure that those remaining are correct.  Here is
an attempt to capture other version changes necessary:</p>
 <ol><li>scm entried in root pom.xml</li><li>assemblies/geronimo-boilerplate-minimal/src/main/underlay/etc/gsh-classworlds.conf</li><li>framework/configs/geronimo-gbean-deployer/src/it/j2ee-system-2/src/test/resources/META-INF/geronimo-plugin.xml</li><li>framework/configs/geronimo-gbean-deployer/src/it/j2ee-system-2/src/test/resources/META-INF/plan.xml</li><li>framework/configs/geronimo-gbean-deployer/src/it/j2ee-system/src/test/resources/META-INF/geronimo-plugin.xml</li><li>framework/configs/geronimo-gbean-deployer/src/it/j2ee-system/src/test/resources/META-INF/plan.xml</li><li>framework/configs/geronimo-gbean-deployer/src/it/metadatageneration-2/src/test/resources/META-INF/geronimo-plugin.xml</li><li>framework/configs/geronimo-gbean-deployer/src/it/metadatageneration/src/test/resources/META-INF/geronimo-plugin.xml</li><li>framework/configs/plugin/src/main/plan/plan.xml</li><li>framework/modules/geronimo-plugin/src/test/resources/geronimo-plugins.xml</li><li>framework/modules/geroni
 mo-upgrade/src/test/data/gbean_1.xml</li><li>framework/modules/geronimo-upgrade/src/test/data/gbean_1_result.xml</li><li>plugins/remote-deploy/geronimo-remote-deploy/src/main/webapp/WEB-INF/geronimo-web.xml</li><li>plugins/welcome/geronimo-welcome/src/main/webapp/WEB-INF/geronimo-web.xml</li><li>testsuite/webservices-testsuite/jaxrpc-tests/jaxrpc-war/src/main/webapp/WEB-INF/geronimo-web.xml</li></ol>
 
 
@@ -282,7 +297,7 @@ Also Note: there are references to versi
 <ol><li>assemblies/geronimo-boilerplate-minimal/pom.xml (RELEASE-NOTES filename)</li><li>framework/configs/geronimo-gbean-deployer/src/it/j2ee-system/pom.xml</li><li>framework/configs/plugin/pom.xml</li><li>framework/configs/pom.xml</li><li>plugins/j2ee/j2ee-deployer/pom.xml</li><li>plugins/client/pom.xml</li><li>plugins/corba/client-corba-yoko/pom.xml</li><li>plugins/j2ee/j2ee-server/pom.xml</li><li>plugins/pom.xml</li><li>configs/plugin/pom.xml
(plugin-repository-list)</li><li>root pom ... pom.xml</li><li>README.txt</li><li>RELEASE_NOTES-*.txt</li></ol>
 
 
-<h4><a shape="rect" name="GeronimoServerReleaseProcess-Updatetheongoingmaintenancebranch"></a>Update
the on-going maintenance branch</h4>
+<h4 id="GeronimoServerReleaseProcess-Updatetheon-goingmaintenancebranch">Update the
on-going maintenance branch</h4>
 <p>Make similar changes in the branch that will continue on for the next release.</p>
 <ol><li>Update poms to the next snapshot version</li><li>Update the
same files referenced above</li><li>rename RELEASE_NOTES-x.y.z.txt as appropriate</li><li>Some
of the "special" updates required are really just applicable here (when creating a new version
rather than just removing the snapshot from an existing version).  This is especially true
for reference to the geronimo plugin repository (which normally named without the snapshot
even when the release is still a snapshot release).</li></ol>
 
@@ -296,20 +311,20 @@ Also Note: there are references to versi
 
 
 
-<h3><a shape="rect" name="GeronimoServerReleaseProcess-Rationale"></a>Rationale</h3>
+<h3 id="GeronimoServerReleaseProcess-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="GeronimoServerReleaseProcess-CreatingaReleaseCandidate"></a>Creating
a Release Candidate</h3>
+<h3 id="GeronimoServerReleaseProcess-CreatingaReleaseCandidate">Creating a Release
Candidate</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>Be
sure that you have your <tt>~/.m2/settings.xml</tt> updated as specified above
in <a shape="rect" href="#GeronimoServerReleaseProcess-staging">Releasing a Geronimo
Project</a></li><li>Copy (or move as per situation, for eg specs) the trunk/branch
to the new branch using the following command.
+<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>Be
sure that you have your <code>~/.m2/settings.xml</code> updated as specified above
in <a shape="rect" href="#GeronimoServerReleaseProcess-staging">Releasing a Geronimo
Project</a></li><li>Copy (or move as per situation, for eg specs) the trunk/branch
to the new branch 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>
-</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;
@@ -318,7 +333,7 @@ Also Note: there are references to versi
 &lt;/scm&gt;
 ]]></script>
 </div></div></li><li>Add the following release profile to the root
pom.xml (Note: This is a subset of the profile included in the maven release process).  This
will utilize the maven gpg plugin to sign the artifacts produced and the maven deploy plugin
to stage the release to your people.apache staging location but will not utilize the maven
release plugin to create the tag, rename versions, etc...
-<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;
@@ -364,7 +379,13 @@ Also Note: there are references to versi
     mvn rat:check
 </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">There
are a few source files that cannot contain license headers due to the expected format of the
file (like LogFactory classes.)  Compare these files against the last release to verify it's
okay to release them without headers and ask the prior release manager and/or dev list for
guidance.</td></tr></table></div></li><li>Stage the maven
artifacts<br clear="none">
+    <div class="aui-message warning shadowed information-macro">
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            <p>There are a few source files that cannot contain license
headers due to the expected format of the file (like LogFactory classes.)  Compare these files
against the last release to verify it's okay to release them without headers and ask the prior
release manager and/or dev list for guidance.</p>
+                    </div>
+    </div>
+</li><li>Stage the maven artifacts<br clear="none">
 When you are ready to create a release candidate, clean out the previous build results from
the branches tree (otherwise assemblies will not be rebuilt correctly) and rebuild (without
tests or testsuite) to now deploy the artifacts to the staging site that will be used for
the release vote using the following command.
 <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
 <pre>Server 2.0.x/2.1.x -
@@ -375,15 +396,21 @@ Server 2.2 -
     mvn -Prelease,no-it 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">Be
extremely careful with this step.  There have been times when a slight modification in the
above command will result in items being deployed directly to the rsync location rather than
to the staging location.<br clear="none">
+    <div class="aui-message warning shadowed information-macro">
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            <p>Be extremely careful with this step.  There have been
times when a slight modification in the above command will result in items being deployed
directly to the rsync location rather than to the staging location.<br clear="none">
 Before running this step, verify that there is a corresponding "staging" or "release" profile
in pom.xml.<br clear="none">
-If there are issues/problems with the deploy to the staging location you may have to stage
to a local repository and then scp the content to an apache staging location.</td></tr></table></div></li><li>Export
and tar/zip the source to be voted on for the release using the following commands:
+If there are issues/problems with the deploy to the staging location you may have to stage
to a local repository and then scp the content to an apache staging location.</p>
+                    </div>
+    </div>
+</li><li>Export and tar/zip the source to be voted on for the release using the
following commands:
 <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
 <pre>svn export https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.2 geronimo-2.1.2-src
 tar -zcvf geronimo-2.1.2-src.tar.gz geronimo-2.1.2-src
 </pre>
 </div></div>
-<p>Also create a zip of the source image.</p></li><li>Create appropriate
md5, sha1, and signatures (asc) for the artifacts added manually.  A script similar to this
can be used to create the checksums and signature:
+Also create a zip of the source image.</li><li>Create appropriate md5, sha1,
and signatures (asc) for the artifacts added manually.  A script similar to this can be used
to create the checksums and signature:
 <div class="panel" style="border-style: solid;border-width: 1px;"><div class="panelHeader"
style="border-bottom-width: 1px;border-bottom-style: solid;"><b>signDist.sh</b></div><div
class="panelContent">
 <p>gpg --print-md MD5 ./geronimo-2.1.2-src.tar.gz &gt; ./geronimo-2.1.2-src.tar.gz.md5<br
clear="none">
 gpg --print-md MD5 ./geronimo-2.1.2-src.zip &gt; ./geronimo-2.1.2-src.zip.md5<br clear="none">
@@ -407,8 +434,20 @@ gpg --armor --output ./NOTICE.txt.asc --
 gpg --armor --output ./LICENSE.txt.asc --detach-sig ./LICENSE.txt<br clear="none">
 gpg --armor --output ./DISCLAIMER.txt.asc --detach-sig ./DISCLAIMER.txt</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>
-<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">You
will need to copy the RELEASE_NOTES-x.x.x.txt from the target location of one of the built
assemblies rather than the root of the branch as the version attributes are updated as part
of the build.</td></tr></table></div></li><li>Update the
plugins site  - <a shape="rect" class="external-link" href="http://cwiki.apache.org/GMOxDEV/steps-to-create-a-plugin-repository-for-a-new-geronimo-release.html">http://cwiki.apache.org/GMOxDEV/steps-to-create-a-plugin-repository-for-a-new-geronimo-release.html</a>
+    <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="aui-message warning shadowed information-macro">
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            <p>You will need to copy the RELEASE_NOTES-x.x.x.txt from
the target location of one of the built assemblies rather than the root of the branch as the
version attributes are updated as part of the build.</p>
+                    </div>
+    </div>
+</li><li>Update the plugins site  - <a shape="rect" class="external-link"
href="http://cwiki.apache.org/GMOxDEV/steps-to-create-a-plugin-repository-for-a-new-geronimo-release.html">http://cwiki.apache.org/GMOxDEV/steps-to-create-a-plugin-repository-for-a-new-geronimo-release.html</a>
 	<ol><li>Update your local ~/.m2/repository/geronimo-plugins.xml file from a
clean server build to:
 		<ol><li>Remove all occurrences of your local repo
 <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
@@ -436,15 +475,15 @@ gpg --armor --output ./DISCLAIMER.txt.as
 <pre>https://svn.apache.org/repos/infra/websites/production/geronimo/content/plugins/geronimo-2.1.3/
 </pre>
 </div></div>
-<p>This will get automatically published on <a shape="rect" class="external-link"
href="http://geronimo.apache.org/plugins/geronimo-2.1.3">http://geronimo.apache.org/plugins/geronimo-2.1.3</a>.</p></li><li>Create
the plugin-repository-list-2.1.4.txt for the on-going maintenance branch with
+This will get automatically published on <a shape="rect" class="external-link" href="http://geronimo.apache.org/plugins/geronimo-2.1.3">http://geronimo.apache.org/plugins/geronimo-2.1.3</a>.</li><li>Create
the plugin-repository-list-2.1.4.txt for the on-going maintenance branch with
 <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
 <pre>http://geronimo.apache.org/plugins/geronimo-2.1.4/
 </pre>
 </div></div></li><li>Create the geronimo-2.1.4 directory for the
on-going maintenance branch and seed it with a copy of the .htaccess from the prior release
and the following geronimo-plugins.xml content (until a 2.1.4-SNAPSHOT build has been published
and new geronimo-plugins.xml file created)
-<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: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;?xml version="1.0" encoding="UTF-8" standalone="yes"?&gt;
-&lt;geronimo-plugin-list xmlns:ns2="http://geronimo.apache.org/xml/ns/attributes-1.2"
xmlns="http://geronimo.apache.org/xml/ns/plugins-1.3"&gt;
+&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;yes&quot;?&gt;
+&lt;geronimo-plugin-list xmlns:ns2=&quot;http://geronimo.apache.org/xml/ns/attributes-1.2&quot;
xmlns=&quot;http://geronimo.apache.org/xml/ns/plugins-1.3&quot;&gt;
 
     &lt;default-repository&gt;http://geronimo.apache.org/plugins/geronimo-2.1.4/&lt;/default-repository&gt;
     &lt;default-repository&gt;http://repo1.maven.org/maven2/&lt;/default-repository&gt;
@@ -457,7 +496,7 @@ gpg --armor --output ./DISCLAIMER.txt.as
 	</li></ol>
 
 
-<h3><a shape="rect" name="GeronimoServerReleaseProcess-CallingaVote"></a>Calling
a Vote</h3>
+<h3 id="GeronimoServerReleaseProcess-CallingaVote">Calling a Vote</h3>
 
 <ol><li>Put it up for a vote along with the staging release you created earlier.
In the vote notice, please include the precise names and versions being voted on (e.g. geronimo-jetty6-javaee5-2.1.3),
the svn revision and urls to the current source along with where the tag will be created.
 	<ol><li>Start a vote thread for the release
@@ -533,7 +572,7 @@ The vote is being canceled due to xxxx a
 	</li></ol>
 
 
-<h3><a shape="rect" name="GeronimoServerReleaseProcess-PublishingaReleaseCandidate"></a>Publishing
a Release Candidate</h3>
+<h3 id="GeronimoServerReleaseProcess-PublishingaReleaseCandidate">Publishing a Release
Candidate</h3>
 
 <ol><li>Copy from the staging repo to the production repo.<br clear="none">
 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. Note: Current version of the stage plugin
is 1.0-alpha-1.<br clear="none">
@@ -545,8 +584,20 @@ Here is an example on how to use the sta
   -DtargetRepositoryId=apache.releases
 </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 but specify the correct version anyway.  The entire
staging repository is synced, not just the given version or the current project.</td></tr></table></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">Also
note, this process has been known to have problems at times if a maven version other than
2.0.8 is used.</td></tr></table></div></li><li>Copy the
distribution content from the staging location to the production repo.<br clear="none">
+    <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 but specify
the correct version anyway.  The entire staging repository is synced, not just the given version
or the current project.</p>
+                    </div>
+    </div>
+
+    <div class="aui-message warning shadowed information-macro">
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            <p>Also note, this process has been known to have problems
at times if a maven version other than 2.0.8 is used.</p>
+                    </div>
+    </div>
+</li><li>Copy the distribution content from the staging location to the production
repo.<br clear="none">
   Check in the distribution content into the appropriate location in <a shape="rect" class="external-link"
href="https://dist.apache.org/repos/dist/release/geronimo/">https://dist.apache.org/repos/dist/release/geronimo/</a>.</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".
@@ -554,7 +605,7 @@ Here is an example on how to use the sta
 </div></div></li><li>Update the Geronimo site download pages with
a new page for the release <a shape="rect" class="external-link" href="http://geronimo.apache.org/downloads.html">Geronimo
Downloads </a>.  Include the list JIRA for know issues by first generating a JIRA query
for the release, right clicking on the XML format and saving the url to inclusion in the download
page.</li><li>Administer the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/GERONIMO">GERONIMO
JIRA project</a> to update the released and unreleased versions</li><li>Update
the <a shape="rect" class="external-link" href="http://geronimo.apache.org">Geronimo
Home Page</a> with a News item that a new Geronimo Server release is available</li><li>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>Final step, is to force
the Confluence 
 Autoexport plugin to run for the following spaces:  Apache Geronimo (GMOxSITE), Apache Geronimo
Project Management (GMOxPMGT), Apache Geronimo 2.1 (GMOxDOC21)</li></ol>
 
 
-<h3><a shape="rect" name="GeronimoServerReleaseProcess-Notice"></a>Notice</h3>
+<h3 id="GeronimoServerReleaseProcess-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>
 



Mime
View raw message