forrest-site-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r1064962 - in /forrest/site: .htaccess dtdx/document-v13.pdf dtdx/document-v20.pdf forrest-issues.html procedures/release/How_to_release.html
Date Sat, 29 Jan 2011 06:08:28 GMT
Author: crossley
Date: Sat Jan 29 06:08:27 2011
New Revision: 1064962

URL: http://svn.apache.org/viewvc?rev=1064962&view=rev
Log:
 Publish from forrestbot

Modified:
    forrest/site/.htaccess
    forrest/site/dtdx/document-v13.pdf
    forrest/site/dtdx/document-v20.pdf
    forrest/site/forrest-issues.html
    forrest/site/procedures/release/How_to_release.html

Modified: forrest/site/.htaccess
URL: http://svn.apache.org/viewvc/forrest/site/.htaccess?rev=1064962&r1=1064961&r2=1064962&view=diff
==============================================================================
--- forrest/site/.htaccess (original)
+++ forrest/site/.htaccess Sat Jan 29 06:08:27 2011
@@ -26,6 +26,7 @@ Redirect /pluginDocs/dev http://forrest.
 RedirectMatch ^/faq(.*) http://forrest.apache.org/docs_0_90/faq$1
 RedirectMatch ^/docs/faq(.*) http://forrest.apache.org/docs_0_90/faq$1
 RedirectMatch ^/changes(.*) http://forrest.apache.org/docs_0_90/changes$1
+RedirectMatch ^(.*)/upgrading_09(.*) http://forrest.apache.org/docs_0_90/upgrading_09$2
 
 Options -MultiViews
 

Modified: forrest/site/dtdx/document-v13.pdf
URL: http://svn.apache.org/viewvc/forrest/site/dtdx/document-v13.pdf?rev=1064962&r1=1064961&r2=1064962&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/dtdx/document-v20.pdf
URL: http://svn.apache.org/viewvc/forrest/site/dtdx/document-v20.pdf?rev=1064962&r1=1064961&r2=1064962&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/forrest-issues.html
URL: http://svn.apache.org/viewvc/forrest/site/forrest-issues.html?rev=1064962&r1=1064961&r2=1064962&view=diff
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Sat Jan 29 06:08:27 2011
@@ -201,21 +201,12 @@ document.write("Last Published: " + docu
 <div id="minitoc-area">
 <ul class="minitoc">
 <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>
 <a href="#%5BFOR-855%5D+verify+the+license+situation+prior+to+each+release">[FOR-855]
verify the license situation prior to each release</a>
 </li>
 <li>
-<a href="#%5BFOR-1184%5D+using+unreleased+code+for+some+supporting+products">[FOR-1184]
using unreleased code for some supporting products</a>
-</li>
-<li>
 <a href="#%5BFOR-1077%5D+new+CreationDate+causes+constant+differences+in+output+pdf+documents">[FOR-1077]
new CreationDate causes constant differences in output pdf documents</a>
 </li>
 <li>
-<a href="#%5BFOR-1069%5D+add+notices+for+US+cryptographic+export+laws">[FOR-1069] add
notices for US cryptographic export laws</a>
-</li>
-<li>
 <a href="#%5BFOR-1208%5D+NPE+exception+when+generating+PDF+that+includes+SVG+to+PNG+image+conversion">[FOR-1208]
NPE exception when generating PDF that includes SVG to PNG image conversion</a>
 </li>
 <li>
@@ -235,14 +226,6 @@ document.write("Last Published: " + docu
           open issues). The listing below is regenerated on each Forrest run.
         </div>
 </div>
-<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>
-<a href="https://issues.apache.org:443/jira/browse/FOR-868">https://issues.apache.org:443/jira/browse/FOR-868</a>
-</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 &lt;a href="https://issues.apache.org:443/jira/browse/FOR-865"
title="Add missing entries to status.xml to generate the changes list"&gt;&lt;strike&gt;FOR-865&lt;/strike&gt;&lt;/a&gt;
&amp;quot;Add missing entries to status.xml to generate the changes list&amp;quot;.</p>
-</div>
 <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">
@@ -259,14 +242,6 @@ B) Scan the whole trunk repository to ad
 &lt;br/&gt;
 C) Remove any author tags.</p>
 </div>
-<a name="%5BFOR-1184%5D+using+unreleased+code+for+some+supporting+products"></a>
-<h2 class="underlined_10">[FOR-1184] using unreleased code for some supporting products</h2>
-<div class="section">
-<p>
-<a href="https://issues.apache.org:443/jira/browse/FOR-1184">https://issues.apache.org:443/jira/browse/FOR-1184</a>
-</p>
-<p>After the last release, an issue was brought to our attention about using unreleased
code from other projects.</p>
-</div>
 <a name="%5BFOR-1077%5D+new+CreationDate+causes+constant+differences+in+output+pdf+documents"></a>
 <h2 class="underlined_10">[FOR-1077] new CreationDate causes constant differences in
output pdf documents</h2>
 <div class="section">
@@ -277,14 +252,6 @@ C) Remove any author tags.</p>
 &lt;br/&gt;
 </p>
 </div>
-<a name="%5BFOR-1069%5D+add+notices+for+US+cryptographic+export+laws"></a>
-<h2 class="underlined_10">[FOR-1069] add notices for US cryptographic export laws</h2>
-<div class="section">
-<p>
-<a href="https://issues.apache.org:443/jira/browse/FOR-1069">https://issues.apache.org:443/jira/browse/FOR-1069</a>
-</p>
-<p>We need to investigate our SVN and add crypto notices as explained at &lt;a
href="http://www.apache.org/licenses/exports/"&gt;http://www.apache.org/licenses/exports/&lt;/a&gt;
and the legal-discuss mail list.</p>
-</div>
 <a name="%5BFOR-1208%5D+NPE+exception+when+generating+PDF+that+includes+SVG+to+PNG+image+conversion"></a>
 <h2 class="underlined_10">[FOR-1208] NPE exception when generating PDF that includes
SVG to PNG image conversion</h2>
 <div class="section">

Modified: forrest/site/procedures/release/How_to_release.html
URL: http://svn.apache.org/viewvc/forrest/site/procedures/release/How_to_release.html?rev=1064962&r1=1064961&r2=1064962&view=diff
==============================================================================
--- forrest/site/procedures/release/How_to_release.html (original)
+++ forrest/site/procedures/release/How_to_release.html Sat Jan 29 06:08:27 2011
@@ -1581,7 +1581,12 @@ svn mkdir plugins/0.10</pre>
           Note that we have copies <a href="https://issues.apache.org/jira/browse/FOR-1210">FOR-1210</a>.
         </li>
         
-<li>Commit all of the above changes.</li>
+<li>
+          Commit all of the above changes. Either wait for the cronjob,
+          or ssh in and do 'svn up'
+        </li>
+        
+<li>Remember that there is then a one hour rsync delay.</li>
         
 <li>Send email to the dev list to remind people about the new docs set docs_0_100
         and that we don't update docs_0_70 set. Also remind about the new release branch
@@ -1596,8 +1601,11 @@ svn mkdir plugins/0.10</pre>
 <p>
         In this phase we'll upload the new Release, wait for it to be available
         on most mirror sites, publish the new website, then announce the release.
+      </p>
+<p>
         The reason for waiting, is because when you send the announcement, most of
         the mirrors need to be up-to-date or your audience will grumble.
+        See various notes below, explaining the delays.
       </p>
 <div class="note">
 <div class="label">Note</div>



Mime
View raw message