xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r846175 - in /websites/staging/xmlgraphics/trunk/content: ./ fop/dev/release.html
Date Fri, 11 Jan 2013 15:01:53 GMT
Author: buildbot
Date: Fri Jan 11 15:01:53 2013
New Revision: 846175

Log:
Staging update by buildbot for xmlgraphics

Modified:
    websites/staging/xmlgraphics/trunk/content/   (props changed)
    websites/staging/xmlgraphics/trunk/content/fop/dev/release.html

Propchange: websites/staging/xmlgraphics/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jan 11 15:01:53 2013
@@ -1 +1 @@
-1431259
+1432082

Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/release.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/release.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/release.html Fri Jan 11 15:01:53 2013
@@ -375,42 +375,12 @@ $(document).ready(function () {
 <p>Edit release notes (<code>README</code> and <code>status.xml</code>
in the root).</p>
 </li>
 <li>
-<p>Add the release to <code>news-data.xml</code> ; remove links to release
notes of older versions from this file.</p>
-</li>
-<li>
-<p>Update the FAQ (<code>faq.xml</code>) to the new release, e.g., update
the answer for "When is the next release planned?".</p>
-</li>
-<li>
 <p>Check and update the copyright year in NOTICE and build.xml.</p>
 </li>
 <li>
-<p>Update the file <code>doap.rdf</code>, and the files <code>index.xml</code>,
<code>site.xml</code>, <code>download.xml</code>, <code>fo.xml</code>,
<code>maillist.xml</code>, and <code>quickstartguide.xml</code> in
directory <code>xdocs</code> for the new version.</p>
-</li>
-<li>
-<p>Update the version numbers in the release column on the compliance page (<code>compliance.xml</code>);
update the compliance in the release column to the current state (development column).</p>
-</li>
-<li>
 <p>Update version number in <code>build.xml</code> (not to be merged back
into trunk).</p>
 </li>
 <li>
-<p>Copy trunk documentation directory to a new directory with the new version number,
and update the <code>.htaccess</code> file for redirections.</p>
-</li>
-<li>
-<p>Copy <code>test/fotree/disabled-testcases.xml</code> and <code>test/layoutengine/disabled-testcases.xml</code>
to the new version directory <code>&lt;version&gt;/fotree/disabled-testcases.xml</code>
and <code>&lt;version&gt;/layoutengine/disabled-testcases.xml</code>.
Copy <code>known-issues.xml</code> to the new version directory. Copy <code>knownissues-overview.xml</code>
from the current to the new version directory, and update the <code>xi:include</code>
links in it.</p>
-</li>
-<li>
-<p>Update the tab names and directories in <code>tabs.xml</code></p>
-</li>
-<li>
-<p>Delete the previous version directory.</p>
-</li>
-<li>
-<p>Update <code>index.xml</code> in the new version directory.</p>
-</li>
-<li>
-<p>Update <code>compiling.xml</code> in the new version directory: change
the introduction for trunk to that for a release.</p>
-</li>
-<li>
 <p>Build the dist files (<code>build[.sh] dist</code>) and upload them
to your web directory on <code>people.apache.org</code></p>
 </li>
 <li>
@@ -465,7 +435,41 @@ $(document).ready(function () {
 <p>Merge the changes of the subversion release branch back into trunk (not the version
number in the build file) and delete the branch.</p>
 </li>
 <li>
-<p>Deploy the updated documentation to the FOP website.</p>
+<p>In CMS doc, copy trunk directory to a new directory with the new version number.</p>
+</li>
+<li>
+<p>In CMS doc, copy following files to the new version directory:</p>
+<ul>
+<li><code>known-issues.mdtext</code> as <code>knownissues-overview.mdtext</code></li>
+</ul>
+</li>
+<li>
+<p>In CMS doc, update all markdown linkIds to the new release (elementids are of the
form <code>[linkId]: fop_version/path_to_page_XXX"</code> at the beginning of
the files):</p>
+<ul>
+<li><code>faq.mdtext</code></li>
+<li><code>fo.mdtext</code></li>
+<li><code>index.mdtext</code></li>
+<li><code>maillist.mdtext</code></li>
+<li><code>quickstartguide.mdtext</code></li>
+</ul>
+</li>
+<li>
+<p>In CMS doc, update the following files to the new release</p>
+<ul>
+<li><code>fop-sidenav.mdtext</code></li>
+<li><code>download.mdtext</code></li>
+<li><code>compliance.mdtext</code> (version number in new release column)</li>
+</ul>
+</li>
+<li>
+<p>In CMS doc, in the new version directory, update the following files:</p>
+<ul>
+<li><code>index.mdtext</code></li>
+<li><code>compiling.mdtext</code> (change the introduction for trunk to
that for a release).</li>
+</ul>
+</li>
+<li>
+<p>Publish the updated documentation to the FOP website.</p>
 </li>
 <li>
 <p>Post announcements on <code>fop-dev</code> and <code>fop-user</code>
and other related mailing lists.</p>



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org


Mime
View raw message