crossley 2002/07/12 22:45:57 Modified: src/documentation/xdocs/plan Tag: cocoon_2_0_3_branch issues-doc.xml Log: Sync docs with HEAD. Revision Changes Path No revision No revision 1.1.2.2 +9 -7 xml-cocoon2/src/documentation/xdocs/plan/issues-doc.xml Index: issues-doc.xml =================================================================== RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/plan/issues-doc.xml,v retrieving revision 1.1.2.1 retrieving revision 1.1.2.2 diff -u -r1.1.2.1 -r1.1.2.2 --- issues-doc.xml 4 Jul 2002 01:41:08 -0000 1.1.2.1 +++ issues-doc.xml 13 Jul 2002 05:45:57 -0000 1.1.2.2 @@ -16,8 +16,11 @@ <s1 title="Issues"> <p> -Certain issues need to be addressed for all current and future -documentation. Please note that many of these issues are being addressed or discussed on the Apache <link href="http://xml.apache.org/forrest/">Forrest</link> Project. +Certain issues need to be addressed for all current and future documentation. +Many of these issues are being addressed and discussed on the +cocoon-docs <link href="../mail-lists.html">mailing list</link>. +Documentation infrastructure issues are also addressed on the Apache +<link href="http://xml.apache.org/forrest/">Forrest</link> Project. </p> <ul> @@ -36,11 +39,10 @@ </li> <li> -The excellent LinkAlarm service is used after each major public release -of Cocoon to help discover any broken external links. (Internal links -are evaluated during the docs build.) Please see the README file at <link href="linkalarm-readme.txt">linkalarm-readme.txt</link> -and help to attend to any issues. However, the site is updated more -frequently now, so the cost of using LinkAlarm may not be wise. We need to take advantage of the capabilities of Cocoon's LinkStatus Generator. Perhaps this can be incorporated into a custom build target for docs. +Cocoon has various tools to assist with monitoring broken hyperlinks. +There is a separate document to explain the +<link href="linkstatus.html">linkstatus</link> and show how you can help to +ensure robustness of the documentation set and the website. </li> <li>
---------------------------------------------------------------------- In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]