forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r924154 - /forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
Date Wed, 17 Mar 2010 04:49:20 GMT
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>



Mime
View raw message