cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache CXF > Release Management
Date Fri, 24 Aug 2012 15:28:00 GMT
    <base href="">
            <link rel="stylesheet" href="/confluence/s/2042/9/15/_/styles/combined.css?spaceKey=CXF&amp;forWysiwyg=true"
<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="">Release
    <h4>Page <b>edited</b> by             <a href="">Glen
        <div id="versionComment">
        info added on where to get JIRA portion of release notes<br />
                         <h4>Changes (1)</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" >h2. Performing a release <br>
            <tr><td class="diff-changed-lines" >The first step is to update the
release_notes.txt in the distribution/src/main/release. <span class="diff-added-words"style="background-color:
#dfd;"> This file&#39;s JIRA list of solved Bugs, Improvements, etc. can be obtained
from the [&quot;Road Map&quot; JIRA tab|],
selecting the desired version&#39;s Release Notes, and then the Configure Release Notes
button (choose Text output).</span> <br></td></tr>
            <tr><td class="diff-unchanged" > <br>Then, to actually perform
the relesae, run the below commands.   <br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
    </div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">
        <h2><a name="ReleaseManagement-Deployingsnapshots"></a>Deploying

<p>Snapshots are automatically deployed every night to the Nexus snapshot repository
at <a href="" class="external-link"
.  There is no need to manually deploy snapshots anymore.</p>

<h2><a name="ReleaseManagement-Maintainingafixesbranch"></a>Maintaining
a fixes branch</h2>
<p>dkulp: I'm adding this section to document what worked for ME when maintaining the
2.0.x-fixes branch for the 2.0.x releases.  Each Release Manager may have their own style
or tools or whatever.   This is not a "set in stone" type thing.  </p>

<p>Basically, almost all development and fixes and such are usually done by the various
developers right on trunk.   Thus, the main job of the fixes branch maintainer is to triage
the commits on trunk and merge pure fixes to the fixes branch, resolve conflicts, run the
tests, and periodically deploy snapshots.   For the most part, when things go well, it doesn't
take too much time or effort.   An hour or two every couple days is about it.</p>

<p>To set up, you'll want to:</p>
	<li>use svn cp to make a branch. Use URLs for the pathnames or it will take <em>forever</em>.</li>
	<li>use bin/ to change the version in the branch</li>
	<li>use init to set up svnmerge. You may want to run this in <em>both</em>
the trunk and the new branch in case you are contemplating bidirectional merges.</li>

<p>These steps work for individual developers who want to go off into a branch in the
sandbox to work through something complex.</p>

<p>In trunk/bin, there is a program that wraps to assist in
the merging.   If the branch is setup with, if you run it from you checkout directory,
it will prompt for every commit on trunk to see if you want to "Merge" it, "Block" it, or
"Ignore" it.   It displays the commit log first so you can see what was involved.   You can
also check the  <a href="" class="external-link"
rel="nofollow">cxf-commits</a> archive to see the full details of the commit to help
decide what action to take.  If you select "Merge", it will merge the change and then prompt
before committing.    That will allow you to look at the merge and resolve any conflicts.
 (or even revert it if you didn't mean to hit Merge)</p>

<h2><a name="ReleaseManagement-Performingarelease"></a>Performing a release</h2>

<p>The first step is to update the release_notes.txt in the distribution/src/main/release.
 This file's JIRA list of solved Bugs, Improvements, etc. can be obtained from the <a href=""
class="external-link" rel="nofollow">"Road Map" JIRA tab</a>, selecting the desired
version's Release Notes, and then the Configure Release Notes button (choose Text output).</p>

<p>Then, to actually perform the relesae, run the below commands.  </p>
<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>It is suggested to use Maven 2.2.1
for CXF versions &lt;=2.5.x as that has been better tested.   For &gt;=2.6.0, Maven
3 is required.  Also, since CXF supports Java5, it is recommended that the release be done
with a Java5 JDK.</td></tr></table></div>
<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
<pre>mvn release:prepare -Peverything,jaxws22
mvn release:perform
<p>That will tag the release, update the poms, etc...  Then build it (off the tag) and
deploy everything (including source jars and javadoc jars) to the Nexus repository location
and gpg signs everything.  When the build is done staging, you need to login to the Nexus
repository and "close" the staging are.    That is very important.   After the staging are
is closed, note the URL for the staging area as you will need that for the vote.</p>
<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>You may encounter
error like<br/>
<a href="/confluence/pages/createpage.action?spaceKey=CXF&amp;title=INFO&amp;linkCreation=true&amp;fromPageId=70605"
class="createlink">INFO</a> Unable to tag SCM<br/>
Provider message:<br/>
The svn tag command failed.<br/>
Command output:<br/>
svn: PROPFIND request failed on '/repos/asf/!svn/vcc/default'<br/>
svn: No such revision 1197023<br/>
when run "mvn release:prepare -Peverything,jaxws22" to create tag if you're not in U.S. <br/>
This is caused by that the svn server in Europe need some time to sync up to the central server
in U.S.<br/>
If you encounter it, just wait a minute, and do "mvn release:prepare -Dresume=true -Peverything,jaxws22"
will pick up the left task from last run.</td></tr></table></div>

<p>At this point, everything "pre-vote" is done.   Call the vote.</p>

<h2><a name="ReleaseManagement-Releasingtheartifacts"></a>Releasing the

	<li>Maven artifacts -  After the vote passes, you'll need to promote that staging repository
to the main location. Login to Nexus to do that as well.  See above Maven team release page.</li>

	<li>Distributions - You will need to commit the distributions into the special svn
distribution area:
<a href="" class="external-link" rel="nofollow"></a><br/>
when the commit done there, they will be live on fairly quickly, but it will
still take time for the mirrors to get copies.   It's likely easier to make the directory
via an svn command, check out just that directory, and then add the files.  The dist area
is rather large (400MB or so) so checking out the entire thing may be slow. 
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-java">
svn mkdir https:<span class="code-comment">//
</span>svn checkout https:<span class="code-comment">//
</span>....  add files to 2.6.3 .....
svn commit

	<li>Update the download page - around 24 hours after committing the distributions,
update the download page, release notes, etc... to point at the new versions.</li>

	<li>Unpack the javadocs from the appropriate cxf-bundle-VERSION-javadocs.jar into the
appropriate directory in an svn checkout of <a href=""
class="external-link" rel="nofollow"></a>
 and commit the new version.  Make sure any new files are added.</li>

	<li>Unpack the schemas directory from the appropriate cxf-bundle-VERSION.jar and check
if any of the schemas in <a href=""
class="external-link" rel="nofollow"></a>
need updating.</li>

        <div id="commentsSection" class="wiki-content pageSection">
        <div style="float: right;">
            <a href=""
class="grey">Change Notification Preferences</a>
        <a href="">View
        <a href="">View
        <a href=";showCommentArea=true#addcomment">Add

View raw message