Author: crossley
Date: Wed Apr 4 01:19:34 2007
New Revision: 525454
URL: http://svn.apache.org/viewvc?view=rev&rev=525454
Log:
Automatic publish from forrestbot
Modified:
forrest/site/docs_0_80/changes.html
forrest/site/docs_0_80/changes.pdf
forrest/site/docs_0_80/changes.rss
forrest/site/docs_0_80/changes.xml
forrest/site/forrest-issues.html
forrest/site/forrest-issues.pdf
forrest/site/procedures/release/How_to_release.html
forrest/site/procedures/release/How_to_release.pdf
forrest/site/svn.html
forrest/site/svn.pdf
Modified: forrest/site/docs_0_80/changes.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/changes.html?view=diff&rev=525454&r1=525453&r2=525454
==============================================================================
--- forrest/site/docs_0_80/changes.html (original)
+++ forrest/site/docs_0_80/changes.html Wed Apr 4 01:19:34 2007
@@ -827,8 +827,8 @@
Committed by TWW. See Issue <a href="http://issues.apache.org/jira/browse/FOR-732">FOR-732</a>.</li>
<li>
<img class="icon" alt="fix" src="../images/fix.jpg">
- After a 'Forrest Clean' , Forrest could not be run in offline mode due to
- not being able to retrieve plugin descriptor files.
+ After doing 'forrest clean' then Forrest could not be run without network access, due to
+ not being able to retrieve plugin descriptor files.
Committed by DC. See Issue <a href="http://issues.apache.org/jira/browse/FOR-927">FOR-927</a>.</li>
<li>
<img class="icon" alt="fix" src="../images/fix.jpg">
Modified: forrest/site/docs_0_80/changes.pdf
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/changes.pdf?view=diff&rev=525454&r1=525453&r2=525454
==============================================================================
Binary files - no diff available.
Modified: forrest/site/docs_0_80/changes.rss
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/changes.rss?view=diff&rev=525454&r1=525453&r2=525454
==============================================================================
--- forrest/site/docs_0_80/changes.rss (original)
+++ forrest/site/docs_0_80/changes.rss Wed Apr 4 01:19:34 2007
@@ -205,8 +205,8 @@
:
- After a 'Forrest Clean' , Forrest could not be run in offline mode due to
- not being able to retrieve plugin descriptor files.
+ After doing 'forrest clean' then Forrest could not be run without network access, due to
+ not being able to retrieve plugin descriptor files.
</description></item>
<item><title>code update
(bug FOR-924)
@@ -5785,8 +5785,8 @@
:
- After a 'Forrest Clean' , Forrest could not be run in offline mode due to
- not being able to retrieve plugin descriptor files.
+ After doing 'forrest clean' then Forrest could not be run without network access, due to
+ not being able to retrieve plugin descriptor files.
</description></item><item><title>code update
(bug FOR-924)
</title><link>changes.html</link><description>code update
Modified: forrest/site/docs_0_80/changes.xml
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/changes.xml?view=diff&rev=525454&r1=525453&r2=525454
==============================================================================
--- forrest/site/docs_0_80/changes.xml (original)
+++ forrest/site/docs_0_80/changes.xml Wed Apr 4 01:19:34 2007
@@ -205,8 +205,8 @@
Fix caching problem that made a restart neccessary after
making a locationmap resource location change.
Committed by TWW. See Issue <link href="http://issues.apache.org/jira/browse/FOR-732">FOR-732</link>.</li><li><icon alt="fix" src="../images/fix.jpg"/>
- After a 'Forrest Clean' , Forrest could not be run in offline mode due to
- not being able to retrieve plugin descriptor files.
+ After doing 'forrest clean' then Forrest could not be run without network access, due to
+ not being able to retrieve plugin descriptor files.
Committed by DC. See Issue <link href="http://issues.apache.org/jira/browse/FOR-927">FOR-927</link>.</li><li><icon alt="fix" src="../images/fix.jpg"/>
When using html as source, the "a" elements were not rendered properly if both
@href and @name attributes. A side-effect of this fix is that now all other
Modified: forrest/site/forrest-issues.html
URL: http://svn.apache.org/viewvc/forrest/site/forrest-issues.html?view=diff&rev=525454&r1=525453&r2=525454
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Wed Apr 4 01:19:34 2007
@@ -195,9 +195,6 @@
<div id="minitoc-area">
<ul class="minitoc">
<li>
-<a href="#%5BFOR-911%5D+decide+content+of+release">[FOR-911] decide content of release</a>
-</li>
-<li>
<a href="#%5BFOR-868%5D+add+relevant+notes+to+the+%22Upgrading%22+xdoc">[FOR-868] add relevant notes to the "Upgrading" xdoc</a>
</li>
<li>
@@ -207,6 +204,9 @@
<a href="#%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo">[FOR-742] trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo</a>
</li>
<li>
+<a href="#%5BFOR-977%5D+The+releaseNotes_*.html+has+Bugzilla+URLs+rather+than+Jira+URLs+for+linked+issues">[FOR-977] The releaseNotes_*.html has Bugzilla URLs rather than Jira URLs for linked issues</a>
+</li>
+<li>
<a href="#%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes">[FOR-241] character entities (e.g. ampersand) are expanded again for href or src attributes</a>
</li>
<li>
@@ -225,19 +225,7 @@
<a href="http://issues.apache.org/jira/secure/IssueNavigator.jspa?pid=12310000&resolutionIds=-1&tempMax=1000&reset=true">all</a> open issues).
The listing below is regenerated on each Forrest run.</div>
</div>
-<a name="N10011"></a><a name="%5BFOR-911%5D+decide+content+of+release"></a>
-<h2 class="underlined_10">[FOR-911] decide content of release</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-911">http://issues.apache.org/jira/browse/FOR-911</a>
-</p>
-<p>For past releases we have essentially done a &quot;source&quot; release, i.e. pack everything found in svn trunk including a pre-built forrest binary jar file.<br/>
-<br/>
-Here is one recent discussion:<br/>
-&nbsp;content of release [was: Re: review list of scheduled issues for 0.8 release]<br/>
-&nbsp;<a href="http://marc.theaimsgroup.com/?t=115257903800001">http://marc.theaimsgroup.com/?t=115257903800001</a></p>
-</div>
-<a name="N1001D"></a><a name="%5BFOR-868%5D+add+relevant+notes+to+the+%22Upgrading%22+xdoc"></a>
+<a name="N10011"></a><a name="%5BFOR-868%5D+add+relevant+notes+to+the+%22Upgrading%22+xdoc"></a>
<h2 class="underlined_10">[FOR-868] add relevant notes to the "Upgrading" xdoc</h2>
<div class="section">
<p>
@@ -245,7 +233,7 @@
</p>
<p>We need to add some notes to the upgrading_0*.html doc for the upcoming release. This would most easily be done after attending to <a href="https://issues.apache.org/jira/browse/FOR-865" title="Add missing entries to status.xml to generate the changes list"><strike>FOR-865</strike></a> &quot;Add missing entries to status.xml to generate the changes list&quot;.</p>
</div>
-<a name="N10029"></a><a name="%5BFOR-855%5D+verify+the+license+situation+prior+to+each+release"></a>
+<a name="N1001D"></a><a name="%5BFOR-855%5D+verify+the+license+situation+prior+to+each+release"></a>
<h2 class="underlined_10">[FOR-855] verify the license situation prior to each release</h2>
<div class="section">
<p>
@@ -260,7 +248,7 @@
B) Scan the whole trunk repository to add missing ASF license headers to source files and to ensure that the ASF license headers have not been accidently added to external files. See etc/relicense.txt<br/>
</p>
</div>
-<a name="N10035"></a><a name="%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo"></a>
+<a name="N10029"></a><a name="%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo"></a>
<h2 class="underlined_10">[FOR-742] trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo</h2>
<div class="section">
<p>
@@ -270,6 +258,14 @@
<br/>
The solution is discussed here:<br/>
<a href="http://marc.theaimsgroup.com/?t=113176328300002">http://marc.theaimsgroup.com/?t=113176328300002</a></p>
+</div>
+<a name="N10035"></a><a name="%5BFOR-977%5D+The+releaseNotes_*.html+has+Bugzilla+URLs+rather+than+Jira+URLs+for+linked+issues"></a>
+<h2 class="underlined_10">[FOR-977] The releaseNotes_*.html has Bugzilla URLs rather than Jira URLs for linked issues</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-977">http://issues.apache.org/jira/browse/FOR-977</a>
+</p>
+<p>The changes_*.html are generated from status.xml and the references to &quot;fixes-bug&quot; issues are correctly constructed as Jira URLs. However the releaseNotes_*.html incorrectly has Bugzilla URLs. IIRC an entry in a site's forrest.properties handles this.</p>
</div>
<a name="N10041"></a><a name="%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes"></a>
<h2 class="underlined_10">[FOR-241] character entities (e.g. ampersand) are expanded again for href or src attributes</h2>
Modified: forrest/site/forrest-issues.pdf
URL: http://svn.apache.org/viewvc/forrest/site/forrest-issues.pdf?view=diff&rev=525454&r1=525453&r2=525454
==============================================================================
Binary files - no diff available.
Modified: forrest/site/procedures/release/How_to_release.html
URL: http://svn.apache.org/viewvc/forrest/site/procedures/release/How_to_release.html?view=diff&rev=525454&r1=525453&r2=525454
==============================================================================
--- forrest/site/procedures/release/How_to_release.html (original)
+++ forrest/site/procedures/release/How_to_release.html Wed Apr 4 01:19:34 2007
@@ -332,7 +332,7 @@
<div class="section">
<p>There are a number of things to be done by the project before the release will start.
Don't leave these until the last minute.
- It is not the Release Manager's job to fix bugs nor address blocker issues. The RM job begins when the
+ It is not the Release Manager's job to fix bugs nor address blocker issues. The RM job begins after the
project is ready to do the release.</p>
<ul>
@@ -342,6 +342,16 @@
<li>The documentation content is ready.</li>
+<li>Supporting products (e.g. Ant, Xerces) should have been updated well before this
+ stage. Do not attempt such upgrades too close to the release, as it
+ will distract attention from other issues and possibly introduce new problems.
+ </li>
+
+<li>Add some issues to the Roadmap for the important general issues that need to
+ happen before the release.
+ Some examples from last time: FOR-911, FOR-868, FOR-865, FOR-855, FOR-644.
+ </li>
+
<li>
<p>Relevant changes are listed in the site-author/status.xml and contributers have been attributed. Other changes are listed in the various plugins/status.xml files.</p>
@@ -381,7 +391,7 @@
</div>
</div>
-<a name="N1006E"></a><a name="PrepProject"></a>
+<a name="N10074"></a><a name="PrepProject"></a>
<h2 class="underlined_10">Preparing the project for the release</h2>
<div class="section">
<p>In this step the Release Manager starts the process to finalise the outstanding blocker issues. </p>
@@ -411,7 +421,7 @@
</div>
-<a name="N10095"></a><a name="PrepRM"></a>
+<a name="N1009B"></a><a name="PrepRM"></a>
<h2 class="underlined_10">Preparations for the Release Manager</h2>
<div class="section">
<p>Particularly the Release Manager, but also anyone assisting, needs to be familiar
@@ -454,7 +464,7 @@
</div>
-<a name="N100C3"></a><a name="PrepRelPlan"></a>
+<a name="N100C9"></a><a name="PrepRelPlan"></a>
<h2 class="underlined_10">Preparing the Release Plan</h2>
<div class="section">
<p>Prepare the Release Plan to define the corner stones of the coming release</p>
@@ -494,7 +504,7 @@
</div>
-<a name="N100F6"></a><a name="PrepCodeBase"></a>
+<a name="N100FC"></a><a name="PrepCodeBase"></a>
<h2 class="underlined_10">Preparing the code base</h2>
<div class="section">
<p>Anyone can help with this phase.</p>
@@ -517,10 +527,22 @@
</li>
<li>
-
-<p>Ensure that documentation is ready.</p>
+ Ensure that documentation structure and conntet is ready.
+ </li>
-</li>
+<li>Ensure that the documentation is building properly, do 'cd site-author; forrest'. Fix any linking errors.</li>
+
+<li>
+ Create a new file, etc/RELEASE-NOTES-x.y.txt, where x.y is the version currently being released.
+ It is best to copy an earlier RELEASE-NOTES file, to keep a common layout.
+ In this file, insert the list of important changes which is obtained by doing:
+ http://localhost:8888/releaseNotes_0.8-dev.txt
+ </li>
+
+<li>
+ Prepare the announcement text. Create a file etc/announcement-x.txt
+ (by 'svn move' the old one) and list the major new features, e.g. locationmap.
+ </li>
<li>
@@ -553,7 +575,7 @@
</div>
-<a name="N10137"></a><a name="PrepTrunk"></a>
+<a name="N10143"></a><a name="PrepTrunk"></a>
<h2 class="underlined_10">Preparing your working copy of SVN trunk</h2>
<div class="section">
<div class="fixme">
@@ -601,7 +623,7 @@
</div>
-<a name="N10168"></a><a name="PrepDistSvn"></a>
+<a name="N10174"></a><a name="PrepDistSvn"></a>
<h2 class="underlined_10">Preparing the "dist" SVN</h2>
<div class="section">
<p>The SVN at
@@ -618,7 +640,7 @@
</div>
-<a name="N1017C"></a><a name="adjustDocs"></a>
+<a name="N10188"></a><a name="adjustDocs"></a>
<h2 class="underlined_10">Preparing docs for next release cycle</h2>
<div class="section">
<p>In this phase we get the docs ready for the release. You will
@@ -731,18 +753,6 @@
<li>Ensure that the documentation is building properly, do 'cd site-author; forrest'. Fix any linking errors.</li>
<li>
- Create a new file, etc/RELEASE-NOTES-x.y.txt, where x.y is the version currently being released.
- It is best to copy an earlier RELEASE-NOTES file, to keep a common layout.
- In this file, insert the list of important changes which is obtained by doing:
- http://localhost:8888/releaseNotes_0.8-dev.txt
- </li>
-
-<li>
- Prepare the announcement text. Create a file etc/announcement-x.txt
- (by 'svn move' the old one) and list the major new features, e.g. locationmap.
- </li>
-
-<li>
<p>Edit the forrest/site-author/content/xdocs/mirrors.html and adjust all version-specific content.</p>
@@ -755,7 +765,7 @@
</div>
-<a name="N101F4"></a><a name="BuildDist"></a>
+<a name="N101FA"></a><a name="BuildDist"></a>
<h2 class="underlined_10">Building the release candidate packages</h2>
<div class="section">
<p>In this phase the Release Manager builds the release candidate to be tested.</p>
@@ -999,7 +1009,7 @@
</div>
-<a name="N102BC"></a><a name="vote"></a>
+<a name="N102C2"></a><a name="vote"></a>
<h2 class="underlined_10">Testing the release candidate and voting</h2>
<div class="section">
<p>Get Forrest developers to test the actual packges on various platforms.</p>
@@ -1061,7 +1071,7 @@
</div>
-<a name="N102F8"></a><a name="FinalRel"></a>
+<a name="N102FE"></a><a name="FinalRel"></a>
<h2 class="underlined_10">Finalizing the release</h2>
<div class="section">
<p>When a good release candidate has been achieved and affirmed by the vote, we'll finalize the release.</p>
@@ -1134,7 +1144,7 @@
</div>
-<a name="N10342"></a><a name="UploadAndAnnounce"></a>
+<a name="N10348"></a><a name="UploadAndAnnounce"></a>
<h2 class="underlined_10">Upload and announcement</h2>
<div class="section">
<p>In this phase we'll upload the new Release, wait for it to be available on most mirror sites, then
@@ -1295,7 +1305,7 @@
</div>
-<a name="N103F8"></a><a name="cleanup"></a>
+<a name="N103FE"></a><a name="cleanup"></a>
<h2 class="underlined_10">Cleanup</h2>
<div class="section">
<ol>
@@ -1377,7 +1387,7 @@
</div>
-<a name="N10446"></a><a name="conclusion"></a>
+<a name="N1044C"></a><a name="conclusion"></a>
<h2 class="underlined_10">Conclusion</h2>
<div class="section">
<p>All done!</p>
Modified: forrest/site/procedures/release/How_to_release.pdf
URL: http://svn.apache.org/viewvc/forrest/site/procedures/release/How_to_release.pdf?view=diff&rev=525454&r1=525453&r2=525454
==============================================================================
Binary files - no diff available.
Modified: forrest/site/svn.html
URL: http://svn.apache.org/viewvc/forrest/site/svn.html?view=diff&rev=525454&r1=525453&r2=525454
==============================================================================
--- forrest/site/svn.html (original)
+++ forrest/site/svn.html Wed Apr 4 01:19:34 2007
@@ -245,7 +245,7 @@
<p>
- Browse the trunk via
+ Developers can browse the trunk via
<a href="http://svn.apache.org/repos/asf/forrest/">direct access</a> or
via the <a href="http://svn.apache.org/viewvc/forrest/trunk">ViewVC web interface</a>.
Similarly branches can be browsed (go up one level).
@@ -258,7 +258,7 @@
</p>
<p>
- To work with the most recent sources rather than a released version,
+ Developers can work with the most recent sources rather than a released version,
follow the <a href="docs_0_80/howto/../build.html">instructions</a> to checkout your working copy.
</p>
Modified: forrest/site/svn.pdf
URL: http://svn.apache.org/viewvc/forrest/site/svn.pdf?view=diff&rev=525454&r1=525453&r2=525454
==============================================================================
Binary files - no diff available.
Date: Wed Apr 4 01:19:34 2007
New Revision: 525454
URL: http://svn.apache.org/viewvc?view=rev&rev=525454
Log:
Automatic publish from forrestbot
Modified:
forrest/site/docs_0_80/changes.html
forrest/site/docs_0_80/changes.pdf
forrest/site/docs_0_80/changes.rss
forrest/site/docs_0_80/changes.xml
forrest/site/forrest-issues.html
forrest/site/forrest-issues.pdf
forrest/site/procedures/release/How_to_release.html
forrest/site/procedures/release/How_to_release.pdf
forrest/site/svn.html
forrest/site/svn.pdf
Modified: forrest/site/docs_0_80/changes.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/changes.html?view=diff&rev=525454&r1=525453&r2=525454
==============================================================================
--- forrest/site/docs_0_80/changes.html (original)
+++ forrest/site/docs_0_80/changes.html Wed Apr 4 01:19:34 2007
@@ -827,8 +827,8 @@
Committed by TWW. See Issue <a href="http://issues.apache.org/jira/browse/FOR-732">FOR-732</a>.</li>
<li>
<img class="icon" alt="fix" src="../images/fix.jpg">
- After a 'Forrest Clean' , Forrest could not be run in offline mode due to
- not being able to retrieve plugin descriptor files.
+ After doing 'forrest clean' then Forrest could not be run without network access, due to
+ not being able to retrieve plugin descriptor files.
Committed by DC. See Issue <a href="http://issues.apache.org/jira/browse/FOR-927">FOR-927</a>.</li>
<li>
<img class="icon" alt="fix" src="../images/fix.jpg">
Modified: forrest/site/docs_0_80/changes.pdf
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/changes.pdf?view=diff&rev=525454&r1=525453&r2=525454
==============================================================================
Binary files - no diff available.
Modified: forrest/site/docs_0_80/changes.rss
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/changes.rss?view=diff&rev=525454&r1=525453&r2=525454
==============================================================================
--- forrest/site/docs_0_80/changes.rss (original)
+++ forrest/site/docs_0_80/changes.rss Wed Apr 4 01:19:34 2007
@@ -205,8 +205,8 @@
:
- After a 'Forrest Clean' , Forrest could not be run in offline mode due to
- not being able to retrieve plugin descriptor files.
+ After doing 'forrest clean' then Forrest could not be run without network access, due to
+ not being able to retrieve plugin descriptor files.
</description></item>
<item><title>code update
(bug FOR-924)
@@ -5785,8 +5785,8 @@
:
- After a 'Forrest Clean' , Forrest could not be run in offline mode due to
- not being able to retrieve plugin descriptor files.
+ After doing 'forrest clean' then Forrest could not be run without network access, due to
+ not being able to retrieve plugin descriptor files.
</description></item><item><title>code update
(bug FOR-924)
</title><link>changes.html</link><description>code update
Modified: forrest/site/docs_0_80/changes.xml
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/changes.xml?view=diff&rev=525454&r1=525453&r2=525454
==============================================================================
--- forrest/site/docs_0_80/changes.xml (original)
+++ forrest/site/docs_0_80/changes.xml Wed Apr 4 01:19:34 2007
@@ -205,8 +205,8 @@
Fix caching problem that made a restart neccessary after
making a locationmap resource location change.
Committed by TWW. See Issue <link href="http://issues.apache.org/jira/browse/FOR-732">FOR-732</link>.</li><li><icon alt="fix" src="../images/fix.jpg"/>
- After a 'Forrest Clean' , Forrest could not be run in offline mode due to
- not being able to retrieve plugin descriptor files.
+ After doing 'forrest clean' then Forrest could not be run without network access, due to
+ not being able to retrieve plugin descriptor files.
Committed by DC. See Issue <link href="http://issues.apache.org/jira/browse/FOR-927">FOR-927</link>.</li><li><icon alt="fix" src="../images/fix.jpg"/>
When using html as source, the "a" elements were not rendered properly if both
@href and @name attributes. A side-effect of this fix is that now all other
Modified: forrest/site/forrest-issues.html
URL: http://svn.apache.org/viewvc/forrest/site/forrest-issues.html?view=diff&rev=525454&r1=525453&r2=525454
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Wed Apr 4 01:19:34 2007
@@ -195,9 +195,6 @@
<div id="minitoc-area">
<ul class="minitoc">
<li>
-<a href="#%5BFOR-911%5D+decide+content+of+release">[FOR-911] decide content of release</a>
-</li>
-<li>
<a href="#%5BFOR-868%5D+add+relevant+notes+to+the+%22Upgrading%22+xdoc">[FOR-868] add relevant notes to the "Upgrading" xdoc</a>
</li>
<li>
@@ -207,6 +204,9 @@
<a href="#%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo">[FOR-742] trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo</a>
</li>
<li>
+<a href="#%5BFOR-977%5D+The+releaseNotes_*.html+has+Bugzilla+URLs+rather+than+Jira+URLs+for+linked+issues">[FOR-977] The releaseNotes_*.html has Bugzilla URLs rather than Jira URLs for linked issues</a>
+</li>
+<li>
<a href="#%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes">[FOR-241] character entities (e.g. ampersand) are expanded again for href or src attributes</a>
</li>
<li>
@@ -225,19 +225,7 @@
<a href="http://issues.apache.org/jira/secure/IssueNavigator.jspa?pid=12310000&resolutionIds=-1&tempMax=1000&reset=true">all</a> open issues).
The listing below is regenerated on each Forrest run.</div>
</div>
-<a name="N10011"></a><a name="%5BFOR-911%5D+decide+content+of+release"></a>
-<h2 class="underlined_10">[FOR-911] decide content of release</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-911">http://issues.apache.org/jira/browse/FOR-911</a>
-</p>
-<p>For past releases we have essentially done a &quot;source&quot; release, i.e. pack everything found in svn trunk including a pre-built forrest binary jar file.<br/>
-<br/>
-Here is one recent discussion:<br/>
-&nbsp;content of release [was: Re: review list of scheduled issues for 0.8 release]<br/>
-&nbsp;<a href="http://marc.theaimsgroup.com/?t=115257903800001">http://marc.theaimsgroup.com/?t=115257903800001</a></p>
-</div>
-<a name="N1001D"></a><a name="%5BFOR-868%5D+add+relevant+notes+to+the+%22Upgrading%22+xdoc"></a>
+<a name="N10011"></a><a name="%5BFOR-868%5D+add+relevant+notes+to+the+%22Upgrading%22+xdoc"></a>
<h2 class="underlined_10">[FOR-868] add relevant notes to the "Upgrading" xdoc</h2>
<div class="section">
<p>
@@ -245,7 +233,7 @@
</p>
<p>We need to add some notes to the upgrading_0*.html doc for the upcoming release. This would most easily be done after attending to <a href="https://issues.apache.org/jira/browse/FOR-865" title="Add missing entries to status.xml to generate the changes list"><strike>FOR-865</strike></a> &quot;Add missing entries to status.xml to generate the changes list&quot;.</p>
</div>
-<a name="N10029"></a><a name="%5BFOR-855%5D+verify+the+license+situation+prior+to+each+release"></a>
+<a name="N1001D"></a><a name="%5BFOR-855%5D+verify+the+license+situation+prior+to+each+release"></a>
<h2 class="underlined_10">[FOR-855] verify the license situation prior to each release</h2>
<div class="section">
<p>
@@ -260,7 +248,7 @@
B) Scan the whole trunk repository to add missing ASF license headers to source files and to ensure that the ASF license headers have not been accidently added to external files. See etc/relicense.txt<br/>
</p>
</div>
-<a name="N10035"></a><a name="%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo"></a>
+<a name="N10029"></a><a name="%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo"></a>
<h2 class="underlined_10">[FOR-742] trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo</h2>
<div class="section">
<p>
@@ -270,6 +258,14 @@
<br/>
The solution is discussed here:<br/>
<a href="http://marc.theaimsgroup.com/?t=113176328300002">http://marc.theaimsgroup.com/?t=113176328300002</a></p>
+</div>
+<a name="N10035"></a><a name="%5BFOR-977%5D+The+releaseNotes_*.html+has+Bugzilla+URLs+rather+than+Jira+URLs+for+linked+issues"></a>
+<h2 class="underlined_10">[FOR-977] The releaseNotes_*.html has Bugzilla URLs rather than Jira URLs for linked issues</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-977">http://issues.apache.org/jira/browse/FOR-977</a>
+</p>
+<p>The changes_*.html are generated from status.xml and the references to &quot;fixes-bug&quot; issues are correctly constructed as Jira URLs. However the releaseNotes_*.html incorrectly has Bugzilla URLs. IIRC an entry in a site's forrest.properties handles this.</p>
</div>
<a name="N10041"></a><a name="%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes"></a>
<h2 class="underlined_10">[FOR-241] character entities (e.g. ampersand) are expanded again for href or src attributes</h2>
Modified: forrest/site/forrest-issues.pdf
URL: http://svn.apache.org/viewvc/forrest/site/forrest-issues.pdf?view=diff&rev=525454&r1=525453&r2=525454
==============================================================================
Binary files - no diff available.
Modified: forrest/site/procedures/release/How_to_release.html
URL: http://svn.apache.org/viewvc/forrest/site/procedures/release/How_to_release.html?view=diff&rev=525454&r1=525453&r2=525454
==============================================================================
--- forrest/site/procedures/release/How_to_release.html (original)
+++ forrest/site/procedures/release/How_to_release.html Wed Apr 4 01:19:34 2007
@@ -332,7 +332,7 @@
<div class="section">
<p>There are a number of things to be done by the project before the release will start.
Don't leave these until the last minute.
- It is not the Release Manager's job to fix bugs nor address blocker issues. The RM job begins when the
+ It is not the Release Manager's job to fix bugs nor address blocker issues. The RM job begins after the
project is ready to do the release.</p>
<ul>
@@ -342,6 +342,16 @@
<li>The documentation content is ready.</li>
+<li>Supporting products (e.g. Ant, Xerces) should have been updated well before this
+ stage. Do not attempt such upgrades too close to the release, as it
+ will distract attention from other issues and possibly introduce new problems.
+ </li>
+
+<li>Add some issues to the Roadmap for the important general issues that need to
+ happen before the release.
+ Some examples from last time: FOR-911, FOR-868, FOR-865, FOR-855, FOR-644.
+ </li>
+
<li>
<p>Relevant changes are listed in the site-author/status.xml and contributers have been attributed. Other changes are listed in the various plugins/status.xml files.</p>
@@ -381,7 +391,7 @@
</div>
</div>
-<a name="N1006E"></a><a name="PrepProject"></a>
+<a name="N10074"></a><a name="PrepProject"></a>
<h2 class="underlined_10">Preparing the project for the release</h2>
<div class="section">
<p>In this step the Release Manager starts the process to finalise the outstanding blocker issues. </p>
@@ -411,7 +421,7 @@
</div>
-<a name="N10095"></a><a name="PrepRM"></a>
+<a name="N1009B"></a><a name="PrepRM"></a>
<h2 class="underlined_10">Preparations for the Release Manager</h2>
<div class="section">
<p>Particularly the Release Manager, but also anyone assisting, needs to be familiar
@@ -454,7 +464,7 @@
</div>
-<a name="N100C3"></a><a name="PrepRelPlan"></a>
+<a name="N100C9"></a><a name="PrepRelPlan"></a>
<h2 class="underlined_10">Preparing the Release Plan</h2>
<div class="section">
<p>Prepare the Release Plan to define the corner stones of the coming release</p>
@@ -494,7 +504,7 @@
</div>
-<a name="N100F6"></a><a name="PrepCodeBase"></a>
+<a name="N100FC"></a><a name="PrepCodeBase"></a>
<h2 class="underlined_10">Preparing the code base</h2>
<div class="section">
<p>Anyone can help with this phase.</p>
@@ -517,10 +527,22 @@
</li>
<li>
-
-<p>Ensure that documentation is ready.</p>
+ Ensure that documentation structure and conntet is ready.
+ </li>
-</li>
+<li>Ensure that the documentation is building properly, do 'cd site-author; forrest'. Fix any linking errors.</li>
+
+<li>
+ Create a new file, etc/RELEASE-NOTES-x.y.txt, where x.y is the version currently being released.
+ It is best to copy an earlier RELEASE-NOTES file, to keep a common layout.
+ In this file, insert the list of important changes which is obtained by doing:
+ http://localhost:8888/releaseNotes_0.8-dev.txt
+ </li>
+
+<li>
+ Prepare the announcement text. Create a file etc/announcement-x.txt
+ (by 'svn move' the old one) and list the major new features, e.g. locationmap.
+ </li>
<li>
@@ -553,7 +575,7 @@
</div>
-<a name="N10137"></a><a name="PrepTrunk"></a>
+<a name="N10143"></a><a name="PrepTrunk"></a>
<h2 class="underlined_10">Preparing your working copy of SVN trunk</h2>
<div class="section">
<div class="fixme">
@@ -601,7 +623,7 @@
</div>
-<a name="N10168"></a><a name="PrepDistSvn"></a>
+<a name="N10174"></a><a name="PrepDistSvn"></a>
<h2 class="underlined_10">Preparing the "dist" SVN</h2>
<div class="section">
<p>The SVN at
@@ -618,7 +640,7 @@
</div>
-<a name="N1017C"></a><a name="adjustDocs"></a>
+<a name="N10188"></a><a name="adjustDocs"></a>
<h2 class="underlined_10">Preparing docs for next release cycle</h2>
<div class="section">
<p>In this phase we get the docs ready for the release. You will
@@ -731,18 +753,6 @@
<li>Ensure that the documentation is building properly, do 'cd site-author; forrest'. Fix any linking errors.</li>
<li>
- Create a new file, etc/RELEASE-NOTES-x.y.txt, where x.y is the version currently being released.
- It is best to copy an earlier RELEASE-NOTES file, to keep a common layout.
- In this file, insert the list of important changes which is obtained by doing:
- http://localhost:8888/releaseNotes_0.8-dev.txt
- </li>
-
-<li>
- Prepare the announcement text. Create a file etc/announcement-x.txt
- (by 'svn move' the old one) and list the major new features, e.g. locationmap.
- </li>
-
-<li>
<p>Edit the forrest/site-author/content/xdocs/mirrors.html and adjust all version-specific content.</p>
@@ -755,7 +765,7 @@
</div>
-<a name="N101F4"></a><a name="BuildDist"></a>
+<a name="N101FA"></a><a name="BuildDist"></a>
<h2 class="underlined_10">Building the release candidate packages</h2>
<div class="section">
<p>In this phase the Release Manager builds the release candidate to be tested.</p>
@@ -999,7 +1009,7 @@
</div>
-<a name="N102BC"></a><a name="vote"></a>
+<a name="N102C2"></a><a name="vote"></a>
<h2 class="underlined_10">Testing the release candidate and voting</h2>
<div class="section">
<p>Get Forrest developers to test the actual packges on various platforms.</p>
@@ -1061,7 +1071,7 @@
</div>
-<a name="N102F8"></a><a name="FinalRel"></a>
+<a name="N102FE"></a><a name="FinalRel"></a>
<h2 class="underlined_10">Finalizing the release</h2>
<div class="section">
<p>When a good release candidate has been achieved and affirmed by the vote, we'll finalize the release.</p>
@@ -1134,7 +1144,7 @@
</div>
-<a name="N10342"></a><a name="UploadAndAnnounce"></a>
+<a name="N10348"></a><a name="UploadAndAnnounce"></a>
<h2 class="underlined_10">Upload and announcement</h2>
<div class="section">
<p>In this phase we'll upload the new Release, wait for it to be available on most mirror sites, then
@@ -1295,7 +1305,7 @@
</div>
-<a name="N103F8"></a><a name="cleanup"></a>
+<a name="N103FE"></a><a name="cleanup"></a>
<h2 class="underlined_10">Cleanup</h2>
<div class="section">
<ol>
@@ -1377,7 +1387,7 @@
</div>
-<a name="N10446"></a><a name="conclusion"></a>
+<a name="N1044C"></a><a name="conclusion"></a>
<h2 class="underlined_10">Conclusion</h2>
<div class="section">
<p>All done!</p>
Modified: forrest/site/procedures/release/How_to_release.pdf
URL: http://svn.apache.org/viewvc/forrest/site/procedures/release/How_to_release.pdf?view=diff&rev=525454&r1=525453&r2=525454
==============================================================================
Binary files - no diff available.
Modified: forrest/site/svn.html
URL: http://svn.apache.org/viewvc/forrest/site/svn.html?view=diff&rev=525454&r1=525453&r2=525454
==============================================================================
--- forrest/site/svn.html (original)
+++ forrest/site/svn.html Wed Apr 4 01:19:34 2007
@@ -245,7 +245,7 @@
<p>
- Browse the trunk via
+ Developers can browse the trunk via
<a href="http://svn.apache.org/repos/asf/forrest/">direct access</a> or
via the <a href="http://svn.apache.org/viewvc/forrest/trunk">ViewVC web interface</a>.
Similarly branches can be browsed (go up one level).
@@ -258,7 +258,7 @@
</p>
<p>
- To work with the most recent sources rather than a released version,
+ Developers can work with the most recent sources rather than a released version,
follow the <a href="docs_0_80/howto/../build.html">instructions</a> to checkout your working copy.
</p>
Modified: forrest/site/svn.pdf
URL: http://svn.apache.org/viewvc/forrest/site/svn.pdf?view=diff&rev=525454&r1=525453&r2=525454
==============================================================================
Binary files - no diff available.