jim         98/06/06 18:49:59

  Modified:    .        how-to-release.html
  Log:
  Some changes
  
  Revision  Changes    Path
  1.41      +11 -3     apache-devsite/how-to-release.html
  
  Index: how-to-release.html
  ===================================================================
  RCS file: /export/home/cvs/apache-devsite/how-to-release.html,v
  retrieving revision 1.40
  retrieving revision 1.41
  diff -u -r1.40 -r1.41
  --- how-to-release.html       1998/06/06 14:03:50     1.40
  +++ how-to-release.html       1998/06/07 01:49:58     1.41
  @@ -71,7 +71,10 @@
     <HR>
     <STRONG>[ Posting the Announcement ]</STRONG><BR>
     <P>
  -  <LI>Once built, <CODE>Announcement</CODE> should be
  +  <LI>Once the tarball is built, give the mirrors a good 24 hours
  +      to get up to sync. This is really important if this this
  +      a final (i.e.: non-beta) release.
  +  <LI>Now, <CODE>Announcement</CODE> should be
         posted to the following places:
      <UL>
       <LI>Unmoderated UseNet newsgroups (should be crossposted)
  @@ -91,6 +94,10 @@
        </UL>
      </UL>
     <P>
  +  <LI>Make sure that <CODE>Announcement.txt</CODE> and
  +      <CODE>Announcement.html</CODE> in <CODE>apache-site</CODE>
  +      in the <CODE>dist</CODE> directory are updated to include
  +      these changes.
     <LI>Bask in the glow
   </OL>
   
  @@ -125,8 +132,9 @@
         from ``<CODE>Apache/1.X.Y-dev</CODE>'' to
         ``<CODE>Apache/1.X.Y</CODE>''. Then also change
         <CODE>APACHE_RELEASE</CODE> in same file from
  -      ``<CODE>1XXYYZZ</CODE>'' to ``<CODE>1XXYY99</CODE>''. The format is
  -      something like <CODE>printf("%d%02d%02d%02d", major, minor, bugfix,
  +      ``<CODE>1XXYYZZ</CODE>'' to ``<CODE>1XXYY<STRONG>99</STRONG></CODE>''.
  +      The format is something like
  +      <CODE>printf("%d%02d%02d%02d", major, minor, bugfix,
         betaseq)</CODE>.<BR>
        <CODE><STRONG>$ vi src/include/httpd.h</STRONG></CODE><BR>
        <CODE><STRONG>$ cvs commit src/include/httpd.h</STRONG></CODE>
  
  
  

Reply via email to