httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wr...@apache.org
Subject cvs commit: apache-devsite how-to-release.html
Date Thu, 28 Jun 2001 00:07:13 GMT
wrowe       01/06/27 17:07:13

  Modified:    .        how-to-release.html
  Log:
    The more things change...
  
  Revision  Changes    Path
  1.73      +7 -0      apache-devsite/how-to-release.html
  
  Index: how-to-release.html
  ===================================================================
  RCS file: /home/cvs/apache-devsite/how-to-release.html,v
  retrieving revision 1.72
  retrieving revision 1.73
  diff -u -r1.72 -r1.73
  --- how-to-release.html	2001/02/28 15:03:52	1.72
  +++ how-to-release.html	2001/06/28 00:07:09	1.73
  @@ -112,6 +112,13 @@
        Then also change <CODE>APACHE_RELEASE</CODE> in the same file from
        ``<CODE>2<EM>XXYY0</EM>00</CODE>'' to ``<CODE>2<EM>XXYY1</EM>00</CODE>''.
     <P>
  +     <STRONG>Note:</STRONG> until Apache 2.0 is of general release quality,
  +     module magic numbers are not enforced.  You must edit <TT>include/ap_mmn.h</TT>
  +     and bump the MODULE_MAGIC_NUMBER_MAJOR prior to rolling the tarball, to assure
  +     beta testers are testing the corresponding .so modules.  <I>This policy will
be
  +     retracted, and coders will be reponsible for mmn bumps, once Apache 2.0 is
  +     officially released.</I>
  +  <P>
    <LI> Make sure your PGP keys are already present in the <CODE>KEYS</CODE>
        file. If they are not, extract your public key using the
        ``<CODE>pgp&nbsp;-kxa</CODE>'' command, add them to the
  
  
  

Mime
View raw message