svn commit: r924154 - /forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml

[email protected]
Newsgroups gmane.text.xml.forrest.cvs
Message-ID <[email protected]>
Author: crossley
Date: Wed Mar 17 04:49:20 2010
New Revision: 924154

URL: http://svn.apache.org/viewvc?rev=924154&view=rev
Log:
Remind about example of "xml entities".

Modified:
    forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml

Modified: forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml?rev=924154&r1=924153&r2=924154&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml (original)
+++ forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml Wed Mar 17 04:49:20 2010
@@ -456,10 +456,12 @@
         these changes after the code-freeze, but do not publish to the website
         until after the release.
       </p>
-      <fixme author="dc">
+      <fixme author="open">
         We definitely need to use automated version number strings where possible.
         It is too easy to miss some, as we did with 0.8 release. 
         We have a set of core xml entities available.
+        Also see the source xml for this document, which utilises entities to
+        manage the version numbers between releases.
       </fixme>
       <ol>
         <li><p>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.