geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache Geronimo Project Management > Geronimo Eclipse Plugin Release Process
Date Thu, 31 Dec 2009 06:09:00 GMT
<html>
<head>
    <base href="http://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/1519/1/1/_/styles/combined.css?spaceKey=GMOxPMGT&amp;forWysiwyg=true"
type="text/css">
    </head>
<body style="background-color: white" bgcolor="white">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
     <h2><a href="http://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+Eclipse+Plugin+Release+Process">Geronimo
Eclipse Plugin Release Process</a></h2>
     <h4>Page <b>edited</b> by             <a href="http://cwiki.apache.org/confluence/display/~daition@gmail.com">delos</a>
    </h4>
     
          <br/>
     <div class="notificationGreySide">
         <h3><a name="GeronimoEclipsePluginReleaseProcess-Steps"></a>Steps</h3>

<ol>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" 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.
<br clear="all" />
<br clear="all" />
<div class='panelMacro'><table class='noteMacro'><colgroup><col width='24'><col></colgroup><tr><td
valign='top'><img src="/confluence/images/icons/emoticons/warning.gif" width="16" height="16"
align="absmiddle" alt="" border="0"></td><td><p><b>Note:</b>
These notes are written for release 2.2.  Change the version number accordingly for your release&#33;</p></td></tr></table></div>
<p><br clear="all" /></p></li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Pick up JIRA list of fixed bugs and new
features from <a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa" rel="nofollow">Release
Notes</a> and defer unresolved JIRAs</li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" 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.
<br clear="all" />
<br clear="all" /></li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> (<a href="https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.2"
rel="nofollow">https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.2</a>)
Copy the <b>trunk</b> to <b>branches</b> using the following command:
<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
<pre>svn copy SRC-URL DEST-URL -m "Reason for this commit"
</pre>
</div></div>
<p>For example:</p>
<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
<pre>svn copy https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/trunk
         https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.2 -m
"Prepare for GEP 2.2 release"
</pre>
</div></div></li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Checkout or update this <b>branches</b>
tree on your machine.
<br clear="all" />
<br clear="all" /></li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Update the &lt;scm&gt; URLs in
the pom.xml to point to the final URL in tags. For example:
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-xml"><span class="code-tag">&lt;scm&gt;</span>
     <span class="code-tag">&lt;connection&gt;</span>scm:svn:https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.2/<span
class="code-tag">&lt;/connection&gt;</span>
     <span class="code-tag">&lt;developerConnection&gt;</span>scm:svn:https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.2/<span
class="code-tag">&lt;/developerConnection&gt;</span>
     <span class="code-tag">&lt;url&gt;</span>https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.2/<span
class="code-tag">&lt;/url&gt;</span>
<span class="code-tag">&lt;/scm&gt;</span>
</pre>
</div></div></li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Build the new <b>branches</b>
tree that will soon be released
<br clear="all" />
<br clear="all" /></li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Build a publicly accessible staging site
so that the reviewers can download the plugins from it.  An example staging site is <a
href="http://people.apache.org/~mcconne/releases/2.2/RC1/staging_site/" rel="nofollow">http://people.apache.org/~mcconne/releases/2.2/RC1/staging_site/</a>
	<ul class="alternate" type="square">
		<li>mirror the structure of the production site <a href="http://www.apache.org/dist/geronimo/eclipse/"
rel="nofollow">http://www.apache.org/dist/geronimo/eclipse/</a></li>
		<li>the deployable and updatesite zip files go in <a href="http://www.apache.org/dist/geronimo/eclipse/2.2"
rel="nofollow">http://www.apache.org/dist/geronimo/eclipse/2.2</a></li>
		<li>the eclipse update site is <a href="http://www.apache.org/dist/geronimo/eclipse/updates"
rel="nofollow">http://www.apache.org/dist/geronimo/eclipse/updates</a><br clear="all"
/>
<br clear="all" /></li>
	</ul>
	</li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Copy the deployable and updatesite zip
files to the staging site.  For example <a href="http://people.apache.org/~mcconne/releases/2.2/RC1/staging_site/"
rel="nofollow">http://people.apache.org/~mcconne/releases/2.2/RC1/staging_site/</a><br
clear="all" />
<br clear="all" /></li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Create the update site by extracting the
updatesite zip to the staging site, for example <a href="http://people.apache.org/~mcconne/releases/2.1.2/RC2/staging_site/updates"
rel="nofollow">http://people.apache.org/~mcconne/releases/2.1.2/RC2/staging_site/updates</a>.
Also include:
	<ul class="alternate" type="square">
		<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Instructions for using the staging site</li>
	</ul>
	</li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Put the staging site up for a vote. 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><col width='24'><col></colgroup><tr><td
valign='top'><img src="/confluence/images/icons/emoticons/check.gif" width="16" height="16"
align="absmiddle" alt="" border="0"></td><td><b>Tips</b><br
/>1. Be certain to use the Release Candidate (RC) acronym in the name as it will not likely
pass on the first vote<br/>
2. Be certain to use the same version numbers as the Geronimo Server (e.g., 2.2)</td></tr></table></div></li>
		<li>The svn urls to the current source and where the tag will be created</li>
		<li>The svn revision levels being voted on along with pointers to the source and build
output files</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="all" />
<br clear="all" /></li>
	</ul>
	</li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Test the staging site by downloading the
adapter from it (using the same instructions in previous step)&nbsp;</li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" 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 How to install GEP page to the v2.1.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.
<br clear="all" />
<br clear="all" /></li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Make sure to start both a <b>[VOTE]</b>
and a <b>[DISCUSS]</b> thread on the Geronimo dev list
<div class='panelMacro'><table class='tipMacro'><colgroup><col width='24'><col></colgroup><tr><td
valign='top'><img src="/confluence/images/icons/emoticons/check.gif" width="16" height="16"
align="absmiddle" alt="" border="0"></td><td><b>Tip</b><br />Be
certain to get enough binding votes according to the Apache Foundation requirements, which
in general stipulates 3 PMC &#43;1 votes (see <a href="http://www.apache.org/foundation/voting.html#ReleaseVotes"
rel="nofollow">http://www.apache.org/foundation/voting.html#ReleaseVotes</a> for
more details)</td></tr></table></div></li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> After the vote has been approved:
	<ul class="alternate" type="square">
		<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" 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 class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" 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> location on 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 class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Ensure that the version subdirectory is
used (e.g., 2.1.2)</li>
		<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" 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 class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Ensure that the file(s) you copy to the
distribution directory have the RCx acronym removed from the filename</li>
		<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" 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:
<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></li>
		<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Similarly, ensure that your GPG public
key is in the /www/www.apache.org/dist/geronimo/KEYS file before publishing anything to the
distribution location
<br clear="all" />
<br clear="all" /></li>
	</ul>
	</li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Ensure that the corresponding <a href="http://apache.org/dist/geronimo/eclipse/"
rel="nofollow"><b>Geronimo Eclipse distribution</b></a> website is updated
automatically and properly with the deployable.zip file and the updatesite.zip file
<br clear="all" />
<br clear="all" /></li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Update the <b>Geronimo Eclipse Update
Site</b> with the contents of the updatesite.zip:
<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><col width='24'><col></colgroup><tr><td
valign='top'><img src="/confluence/images/icons/emoticons/forbidden.gif" width="16"
height="16" align="absmiddle" alt="" border="0"></td><td><b>Warning</b><br
/>Never delete old releases from the update site - always append to it &#33;&#33;
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><col width='24'><col></colgroup><tr><td
valign='top'><img src="/confluence/images/icons/emoticons/forbidden.gif" width="16"
height="16" align="absmiddle" alt="" border="0"></td><td><b>Warning</b><br
/>If you use FTP to transfer the files to the <b>Geronimo Eclipse Update Site</b>
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>
</ol>


<ul class="alternate" type="square">
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" 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>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" 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:
<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></li>
</ul>


<ol>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Ensure that corresponding <a href="http://apache.org/dist/geronimo/eclipse/updates/"
rel="nofollow"><b>Geronimo Eclipse Update Site</b></a> website (<a
href="http://apache.org/dist/geronimo/eclipse/updates/" rel="nofollow">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="all" />
<br clear="all" /></li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Move the <b>branches</b> tree
to <b>tags</b> using the following command:
<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
<pre>svn move SRC-URL DEST-URL -m "Reason for this commit".
</pre>
</div></div> For example:
<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
<pre>svn move https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.1.2
         https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.1.2 -m "Tagging
GEP 2.1.2"
</pre>
</div></div>
	<ul class="alternate" type="square">
		<li>Follow what the server does.  A maintenance branch for the next dot release (2.1.3)
may be created later by copying the 2.1.2 tag to a 2.1.3 branch.</li>
	</ul>
	</li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Merge changes from <b>tags</b>
into <b>trunk</b> to ensure they are in sync (except for the assembly pom.xml
described above)
<br clear="all" />
<br clear="all" /></li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> update the How to Install GEP page(s)
as described above.
<br clear="all" />
<br clear="all" /></li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Update version number in <b>trunk</b>
(e.g., 2.1.2 &#45;&gt; 2.1.3)
	<ul class="alternate" type="square">
		<li>Be careful / give some thought to the next version number.  ie, 2.2 vs. 2.1.3.
 I think the best choice is to follow the server.
<br clear="all" />
<br clear="all" /></li>
	</ul>
	</li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Update Geronimo version number in <b>trunk</b>
(e.g., 2.1.2 &#45;&gt; 2.1.3-SNAPSHOT)
<br clear="all" />
<br clear="all" /></li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Rename PLUGIN_RELEASE-NOTES-2.1.2.txt
to PLUGIN_RELEASE-NOTES-2.1.3.txt.
<br clear="all" />
<br clear="all" /></li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Update the <a href="http://geronimo.apache.org/development-tools.html"
rel="nofollow">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)
<br clear="all" />
<br clear="all" /></li>
	</ul>
	</li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Administer the <a href="https://issues.apache.org/jira/browse/GERONIMODEVTOOLS"
rel="nofollow">GERONIMODEVTOOLS JIRA project</a> to update the released and unreleased
versions
<br clear="all" />
<br clear="all" /></li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Update the <a href="http://geronimo.apache.org"
rel="nofollow">Geronimo Home Page</a> with a News item that we have an updated Geronimo
Eclipse Plugin available
<br clear="all" />
<br clear="all" /></li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Final step is to update the <a href="http://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Release+Roadmaps"
rel="nofollow">Geronimo Release Roadmaps</a> with the release date.</li>
</ol>

     </div>
     <div id="commentsSection" class="wiki-content pageSection">
       <div style="float: right;">
            <a href="http://cwiki.apache.org/confluence/users/viewnotifications.action"
class="grey">Change Notification Preferences</a>
       </div>

       <a href="http://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+Eclipse+Plugin+Release+Process">View
Online</a>
       |
       <a href="http://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=63893&revisedVersion=149&originalVersion=148">View
Change</a>
              |
       <a href="http://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+Eclipse+Plugin+Release+Process?showComments=true&amp;showCommentArea=true#addcomment">Add
Comment</a>
            </div>
</div>
</div>
</div>
</div>
</body>
</html>

Mime
View raw message