cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r832610 - in /websites/production/cxf/content: cache/main.pageCache release-management.html
Date Thu, 20 Sep 2012 18:47:26 GMT
Author: buildbot
Date: Thu Sep 20 18:47:26 2012
New Revision: 832610

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/main.pageCache
    websites/production/cxf/content/release-management.html

Modified: websites/production/cxf/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/cxf/content/release-management.html
==============================================================================
--- websites/production/cxf/content/release-management.html (original)
+++ websites/production/cxf/content/release-management.html Thu Sep 20 18:47:26 2012
@@ -156,8 +156,6 @@ Apache CXF -- Release Management
 <p>In trunk/bin, there is a DoMerges.java program that wraps svnmerge.py to assist
in the merging.   If the branch is setup with snvmerge.py, 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 shape="rect" class="external-link" href="http://www.nabble.com/cxf-commits-f23851.html"
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 shape="rect" 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 shape="rect"
class="external-link" href="https://issues.apache.org/jira/browse/CXF#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel">"Road
Map" JIRA tab</a>, selecting the desired version's Release Notes, and then the Configure
Release Notes button (choose Text output).</p>
@@ -185,7 +183,7 @@ mvn release:perform
 </div></div>
 <p>The above commands tag the release, update the poms versions, etc., then build it
(off the tag), gpg sign and deploy everything (including source jars and javadoc jars) to
the <a shape="rect" class="external-link" href="https://repository.apache.org">Nexus
repository location</a>.  When the build is done staging, you next need to login to
the Nexus repository and "close" the staging area (click on Staging Repositories in the left-side
menu, select the repo you just uploaded and then select the close button.)   Closing is very
important.   After the staging area 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 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">You
may encounter error like<br clear="none">
-<a shape="rect" class="createlink" href="https://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=CXF&amp;title=INFO&amp;linkCreation=true&amp;fromPageId=70605">INFO</a>
Unable to tag SCM<br clear="none">
+<span class="error">[INFO]</span> Unable to tag SCM<br clear="none">
 Provider message:<br clear="none">
 The svn tag command failed.<br clear="none">
 Command output:<br clear="none">
@@ -226,6 +224,17 @@ svn commit
 
 
 <ul><li>Unpack the schemas directory from the appropriate cxf-bundle-VERSION.jar
and check if any of the schemas in <a shape="rect" class="external-link" href="https://svn-master.apache.org/repos/infra/websites/production/cxf/content/schemas">https://svn-master.apache.org/repos/infra/websites/production/cxf/content/schemas</a>
need updating.</li></ul>
+
+
+<h2><a shape="rect" name="ReleaseManagement-UpdatingJIRA"></a>Updating
JIRA</h2>
+
+<p>JIRA will need to be updated:</p>
+<ul><li>Add new versions that JIRA items can be created against, and mark the
version(s) you just released as "released":</li></ul>
+<ol><li>Go to the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/CXF">CXF
JIRA Home Page</a> and select the "Versions" left menu item, then select "Manage Versions".</li><li>Select
the tools icon (far right side) for the version(s) you've just released and select "Release".</li><li>Also
on this screen type in new release versions for the branch(es) you've released and plan on
releasing more versions from.</li></ol>
+<ul><li>Close the JIRA items that were marked resolved for each release:</li></ul>
+<ol><li>From the previous screen, select "Exit Administration".</li><li>From
the CXF JIRA home page, select Versions from the left-side menu, and for each version you
just released:
+	<ol><li>Select version, then issues left-side menu item, then select the "Resolved"
list.</li><li>From the tools icon, select Bulk Change -&gt; select all items
-&gt; Transition Issues -&gt; Close Issues -&gt; Confirm.</li></ol>
+	</li></ol>
 </div>
            </div>
            <!-- Content -->



Mime
View raw message