forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r410768 - /forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
Date Thu, 01 Jun 2006 05:53:24 GMT
Author: crossley
Date: Wed May 31 22:53:24 2006
New Revision: 410768

URL: http://svn.apache.org/viewvc?rev=410768&view=rev
Log:
Remove fixme note about 'svn status --no-ignore'. The RM needs to be familiar
with doing it anyway for later in the process.

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=410768&r1=410767&r2=410768&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 May
31 22:53:24 2006
@@ -190,8 +190,8 @@
                 easily and - if possible - roll them forward later. So creating an svn branch
for the rc seems to make
                 sense to me.
                 Probably
-                easiest would be to create an rc branch here and co that. I'd sacrifice the
alternative approach for
-                that which is far too risky for my liking anyway. wdyt?</fixme>
+                easiest would be to create an rc branch here and co that.
+                wdyt?</fixme>
 
             <p>In this step you make absolutely sure that your working copy of SVN
trunk has no local modifications, or additional files that you have been fiddling with, and
especially files that might be hidden by svn:ignore settings.
             </p>



Mime
View raw message