We sent that announcement out twice, sigh.  It is not inconceivable that
I approved a second posting but I doubt it.   I recall thinking 
"Oh no, not with that From address.", but then I don't recall thinking
"We already sent this."

Meanwhile, we ought to PGP sign the posted announcments.

Index: how-to-release.html
===================================================================
RCS file: /home/cvs/apache-devsite/how-to-release.html,v
retrieving revision 1.72
diff -u -3 -r1.72 how-to-release.html
--- how-to-release.html 2001/02/28 15:03:52     1.72
+++ how-to-release.html 2001/05/27 17:36:44
@@ -443,8 +443,13 @@
       to get up to sync. This is really important if this this
       a final (i.e.: non-beta) release.
  <p>
- <li>Now, <code>Announcement</code> should be
-      posted to the following places:
+
+ <li>Now, <code>Announcement</code> should be PGP signed by the
+     release manager and posted to the following places.  Please
+     post from the email address of a real human, i.e. don't use
+     [EMAIL PROTECTED]  You may prefer to send using your 
+     apache.org email address.  It's ok if that isn't the user
+     id on the PGP key you sign with.
   <ul>
        <li>Unmoderated UseNet newsgroups (should be crossposted)
         <ul>


 - ben

Reply via email to