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 Mon, 13 Dec 2010 04:29:00 GMT
<html>
<head>
    <base href="https://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/1810/9/1/_/styles/combined.css?spaceKey=GMOxPMGT&amp;forWysiwyg=true"
type="text/css">
    </head>
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="https://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="https://cwiki.apache.org/confluence/display/~hanhongfang">Han
Hong Fang</a>
    </h4>
        <br/>
                         <h4>Changes (3)</h4>
                                 
    
<div id="page-diffs">
            <table class="diff" cellpadding="0" cellspacing="0">
            <tr><td class="diff-snipped" >...<br></td></tr>
            <tr><td class="diff-unchanged" >## Extract geronimo-eclipse-plugin-2.2-updatesite.zip
and calculate check sum for each files <br>## upload all the files into update site
<br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">#
(/) Put the staging site up for a vote. In the vote notice, please include: <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">#
(/) Test the staging site by downloading the adapter from it <br># (/) 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&#39;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&#39;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. <br>\\ <br>\\ <br># (/) Make sure to start a *\[VOTE\]* thread
on the Geronimo dev list. In the vote notice, please include: <br></td></tr>
            <tr><td class="diff-unchanged" >#- 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)
<br>{tip:title=Tips}1. Be certain to use the Release Candidate (RC) acronym in the name
as it will not likely pass on the first vote <br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
            <tr><td class="diff-unchanged" >\\ <br>\\ <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">#
(/) Test the staging site by downloading the adapter from it <br># (/) 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&#39;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&#39;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. <br>\\ <br>\\ <br># (/) Make sure to start both a *\[VOTE\]* thread
on the Geronimo dev list <br></td></tr>
            <tr><td class="diff-unchanged" >{tip:title=Tip}Be certain to get enough
binding votes according to the Apache Foundation requirements, which in general stipulates
3 PMC \+1 votes (see [http://www.apache.org/foundation/voting.html#ReleaseVotes] for more
details) <br>{tip} <br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
        </table>
</div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">
        <h3><a name="GeronimoEclipsePluginReleaseProcess-Steps"></a>Steps</h3>

<p>&nbsp;&nbsp; &nbsp; &nbsp;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 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.&nbsp;</li>
	<li><br class="atl-forced-newline" />
<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><b>Note:</b> These
notes are written for release 2.2.  Change the version number accordingly for your release&#33;</td></tr></table></div>
<p><br class="atl-forced-newline" /></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" class="external-link"
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.&nbsp;</li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Remove snapshot from version number of
dependency. Eg. geronimo-kernel-2.2-SNAPSHOT.jar in MANIFEST.MF of runtime.v22.&nbsp;</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</li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" 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 class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Prepare the release with maven release
plugin. Refer to <a href="http://maven.apache.org/developers/release/apache-release.html"
class="external-link" rel="nofollow">http://maven.apache.org/developers/release/apache-release.html</a>
	<ol>
		<li>mvn release:prepare</li>
		<li>mvn release:perform</li>
	</ol>
	</li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Set up a staging site for verifying update
site at people.apache.org. Eg. &nbsp;<a href="http://people.apache.org/builds/geronimo/eclipse/updates/"
class="external-link" rel="nofollow">http://people.apache.org/builds/geronimo/eclipse/updates/</a>,
this staging site locates at www/people.apache.org/builds/geronimo/eclipse/updates directory
on people.apache.org server
	<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>
	</ol>
	</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</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.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.
<br class="atl-forced-newline" />
<br class="atl-forced-newline" /></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 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><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>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 class="atl-forced-newline" />
<br class="atl-forced-newline" />
<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"
class="external-link" rel="nofollow">http://www.apache.org/foundation/voting.html#ReleaseVotes</a>
for more details)</td></tr></table></div></li>
	</ul>
	</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"/> &nbsp;Promote artifacts in maven staging
site. You may find them on&nbsp;<a href="http://repository.apache.org/" class="external-link"
rel="nofollow">http://repository.apache.org/</a></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 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 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
<br class="atl-forced-newline" />
<br class="atl-forced-newline" /></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/"
class="external-link" 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 class="atl-forced-newline" />
<br class="atl-forced-newline" /></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>
<p>NOTE: To generate keys, you need to notice the rules here <a href="http://www.apache.org/dev/openpgp.html#sha1"
class="external-link" rel="nofollow">http://www.apache.org/dev/openpgp.html</a>and
<a href="http://www.apache.org/dev/key-transition.html" class="external-link" rel="nofollow">http://www.apache.org/dev/key-transition.html</a><br/>
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 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:
	<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><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 &#42;Geronimo Eclipse Update Site&nbsp;*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 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>
	</ol>
	</li>
	<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/"
class="external-link" rel="nofollow"><b>Geronimo Eclipse Update Site</b></a>
website (<a href="http://apache.org/dist/geronimo/eclipse/updates/" class="external-link"
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 class="atl-forced-newline" /></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"
class="external-link" 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 class="atl-forced-newline" />
<br class="atl-forced-newline" /></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"
class="external-link" rel="nofollow">GERONIMODEVTOOLS JIRA project</a> to update
the released and unreleased versions. Remember to mark the version as released.
<br class="atl-forced-newline" />
<br class="atl-forced-newline" /></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"
class="external-link" rel="nofollow">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&nbsp;<a href="mailto:announce@apache.org" class="external-link"
rel="nofollow">announce@apache.org</a>.
<br class="atl-forced-newline" />
<br class="atl-forced-newline" /></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"
class="external-link" rel="nofollow">Geronimo Release Roadmaps</a> with the release
date.</li>
	<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" 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 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.</li>
		<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Update version in plugin.xml from 2.1.2
to 2.1.3</li>
		<li><img class="emoticon" src="/confluence/images/icons/emoticons/check.gif" height="16"
width="16" align="absmiddle" alt="" border="0"/> Update version in MANIFEST.MF from 2.1.2
to 2.1.3</li>
	</ol>
	</li>
</ol>

    </div>
        <div id="commentsSection" class="wiki-content pageSection">
        <div style="float: right;">
            <a href="https://cwiki.apache.org/confluence/users/viewnotifications.action"
class="grey">Change Notification Preferences</a>
        </div>
        <a href="https://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+Eclipse+Plugin+Release+Process">View
Online</a>
        |
        <a href="https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=63893&revisedVersion=171&originalVersion=170">View
Changes</a>
                |
        <a href="https://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