svn commit: r1338887 - /subversion/site/publish/docs/community-guide/releasing.part.html

[ph...@apache.org]

Author: philip
Date: Tue May 15 21:02:09 2012
New Revision: 1338887

URL: http://svn.apache.org/viewvc?rev=1338887&view=rev
Log:
* docs/community-guide/releasing.part.html: Note an effect of move-to-dist.

Modified:
    subversion/site/publish/docs/community-guide/releasing.part.html

Modified: subversion/site/publish/docs/community-guide/releasing.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/releasing.part.html?rev=1338887&r1=1338886&r2=1338887&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Tue May 15 21:02:09 2012
@@ -965,8 +965,12 @@ There is a release.py subcommand that au
 release.py move-to-dist 1.7.0
 </pre>
 It takes the mirrors up to 24 hours to get pick up the new release.
-The archive will also automatically pick up the release.
-</p>
+The archive will also automatically pick up the release.  While
+running move-to-dist will move the signature files committers are
+still able to commit new signatures to <tt>^/release/subversion<tt>
+however it will take up to 24 hours for those signatures to mirror.
+Any such signatures cannot be included in the release announcement
+unless 24 hours have passed since they were committed.</p>
 
 <p>At this point, the release may be publicly available, but its still a good
 idea to hold off on announcing it until after the mirrors have picked it up.