Hi list, I've updated the release page, taking into account that doc is now in CMS.
All changes that were made before on xdoc subdir have been removed, including update for doap.rdf or news-data.xml. You can check the changes, comparing [1] production site and [2] staging site. If there is no objection, I'll publish change on production site next week. [1] http://xmlgraphics.apache.org/fop/dev/release.html [2] http://xmlgraphics.staging.apache.org/fop/dev/release.html 2013/1/11 <psan...@apache.org>: > Author: psancho > Date: Fri Jan 11 15:01:40 2013 > New Revision: 1432082 > > URL: http://svn.apache.org/viewvc?rev=1432082&view=rev > Log: > Update release page taking into account the CMS doc > > Modified: > xmlgraphics/site/trunk/content/fop/dev/release.mdtext > > Modified: xmlgraphics/site/trunk/content/fop/dev/release.mdtext > URL: > http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/release.mdtext?rev=1432082&r1=1432081&r2=1432082&view=diff > > ============================================================================== > --- xmlgraphics/site/trunk/content/fop/dev/release.mdtext (original) > +++ xmlgraphics/site/trunk/content/fop/dev/release.mdtext Fri Jan 11 > 15:01:40 2013 > @@ -24,30 +24,10 @@ The checklist below is based on a combin > > - Edit release notes (`README` and `status.xml` in the root). > > -- Add the release to `news-data.xml` ; remove links to release notes of > older versions from this file. > - > -- Update the FAQ (`faq.xml`) to the new release, e.g., update the answer > for "When is the next release planned?". > - > - Check and update the copyright year in NOTICE and build.xml. > > -- Update the file `doap.rdf`, and the files `index.xml`, `site.xml`, > `download.xml`, `fo.xml`, `maillist.xml`, and `quickstartguide.xml` in > directory `xdocs` for the new version. > - > -- Update the version numbers in the release column on the compliance page > (`compliance.xml`); update the compliance in the release column to the > current state (development column). > - > - Update version number in `build.xml` (not to be merged back into > trunk). > > -- Copy trunk documentation directory to a new directory with the new > version number, and update the `.htaccess` file for redirections. > - > -- Copy `test/fotree/disabled-testcases.xml` and > `test/layoutengine/disabled-testcases.xml` to the new version directory > `<version>/fotree/disabled-testcases.xml` and > `<version>/layoutengine/disabled-testcases.xml`. Copy `known-issues.xml` to > the new version directory. Copy `knownissues-overview.xml` from the current > to the new version directory, and update the `xi:include` links in it. > - > -- Update the tab names and directories in `tabs.xml` > - > -- Delete the previous version directory. > - > -- Update `index.xml` in the new version directory. > - > -- Update `compiling.xml` in the new version directory: change the > introduction for trunk to that for a release. > - > - Build the dist files (`build[.sh] dist`) and upload them to your web > directory on `people.apache.org` > > - Ask on `fop-dev` ML to check the branch and the generated dist files > for errors. > @@ -84,7 +64,28 @@ The checklist below is based on a combin > > - Merge the changes of the subversion release branch back into trunk (not > the version number in the build file) and delete the branch. > > -- Deploy the updated documentation to the FOP website. > +- In CMS doc, copy trunk directory to a new directory with the new > version number. > + > +- In CMS doc, copy following files to the new version directory: > + - `known-issues.mdtext` as `knownissues-overview.mdtext` > + > +- In CMS doc, update all markdown linkIds to the new release (elementids > are of the form `[linkId]: fop_version/path_to_page_XXX"` at the beginning > of the files): > + - `faq.mdtext` > + - `fo.mdtext` > + - `index.mdtext` > + - `maillist.mdtext` > + - `quickstartguide.mdtext` > + > +- In CMS doc, update the following files to the new release > + - `fop-sidenav.mdtext` > + - `download.mdtext` > + - `compliance.mdtext` (version number in new release column) > + > +- In CMS doc, in the new version directory, update the following files: > + - `index.mdtext` > + - `compiling.mdtext` (change the introduction for trunk to that for a > release). > + > +- Publish the updated documentation to the FOP website. > > - Post announcements on `fop-dev` and `fop-user` and other related > mailing lists. -- pascal
