river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r790513 - /websites/staging/river/trunk/content/building-a-release.html
Date Mon, 06 Jun 2011 09:38:23 GMT
Author: buildbot
Date: Mon Jun  6 09:38:23 2011
New Revision: 790513

Log:
Staging update by buildbot

Modified:
    websites/staging/river/trunk/content/building-a-release.html

Modified: websites/staging/river/trunk/content/building-a-release.html
==============================================================================
--- websites/staging/river/trunk/content/building-a-release.html (original)
+++ websites/staging/river/trunk/content/building-a-release.html Mon Jun  6 09:38:23 2011
@@ -80,6 +80,22 @@
 <li>River-trunk should run successful.</li>
 <li>River-verify should run successful. (not yet?)</li>
 </ul>
+<h2 id="gather_release_notes_from_jira">Gather Release Notes From Jira</h2>
+<p>First <a href="https://issues.apache.org/jira/secure/project/ViewProject.jspa?pid=12310600">manage
the versions</a> of River using Jira.  Make sure there is an appropriate release that
Jira issues are have been assigned to.  You can then view the <a href="https://issues.apache.org/jira/browse/RIVER#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel">Roadmap</a>
screen in Jira to create the release and make sure that the correct Jira issues are associated
to it.</p>
+<p>Move the Jira issues around appropriately, especially if you're releasing before
all the issues have been resolves.  In this case, you need to postpone the remaining issues
until a later release.</p>
+<p>You can then use Jira to generate the release notes.  This is done Road Map --&gt;
Release --&gt; Summary --&gt; Release Notes (next to "Filters").</p>
+<p>The release notes need to be pasted into;</p>
+<div class="codehilite"><pre><span class="n">river</span><span
class="sr">/trunk/s</span><span class="n">rc</span><span class="o">-</span><span
class="n">doc</span><span class="sr">/static/</span><span class="n">release</span><span
class="o">-</span><span class="n">notes</span><span class="o">/</span><span
class="nb">index</span><span class="o">.</span><span class="n">html</span>
+</pre></div>
+
+
+<h2 id="update_version_numbers">Update Version Numbers</h2>
+<p>There are version numbers in the following places that need to be updated with the
new release number/name.</p>
+<ul>
+<li>com.sun.jini.constants.VersionConstants.java (SERVER_VERSION)</li>
+<li>river/trunk/src-doc/static/release-notes/index.html (version number)</li>
+</ul>
+<p>In the above HTML page, there is also a section on "changes by component" which
should also be updated.  This should be easy to do by referring to the Jira-generated release
notes.</p>
 <h2 id="branch_the_repository">Branch the repository</h2>
 <div class="codehilite"><pre><span class="n">svn</span> <span
class="n">cp</span> <span class="n">https:</span><span class="sr">//s</span><span
class="n">vn</span><span class="o">.</span><span class="n">apache</span><span
class="o">.</span><span class="n">org</span><span class="sr">/repos/</span><span
class="n">asf</span><span class="sr">/river/</span><span class="n">jtsk</span><span
class="sr">/trunk https://svn.apache.org/</span><span class="n">repos</span><span
class="sr">/asf/</span><span class="n">river</span><span class="sr">/jtsk/</span><span
class="n">branches</span><span class="o">/</span><span class="nv">$VERSION</span>
 </pre></div>
@@ -90,8 +106,6 @@
 </pre></div>
 
 
-<h2 id="gather_release_notes_from_jira">Gather Release Notes From Jira</h2>
-<p>...</p>
 <h2 id="build_the_release_products">Build the release products</h2>
 <div class="codehilite"><pre><span class="n">ant</span> <span
class="o">-</span><span class="n">Dversion</span><span class="o">=</span><span
class="nv">$VERSION</span> <span class="n">clean</span> <span class="n">release</span>
 </pre></div>



Mime
View raw message