You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by di...@apache.org on 2001/10/12 00:47:41 UTC
cvs commit: apache-devsite binaries.html how-to-release.html
dirkx 01/10/11 15:47:41
Modified: . binaries.html how-to-release.html
Log:
Popping in suggestion for the moment at which to move binaries into the tree
Revision Changes Path
1.25 +17 -5 apache-devsite/binaries.html
Index: binaries.html
===================================================================
RCS file: /home/cvs/apache-devsite/binaries.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- binaries.html 2001/06/21 10:52:31 1.24
+++ binaries.html 2001/10/11 22:47:41 1.25
@@ -80,17 +80,24 @@
<CODE>CFLAGS=-Dfoobar src/helpers/binbuild.sh</CODE>.
<P>
-Feel free to create PGP or MD5 signatures:
+Feel encouraged to create PGP or MD5 signatures:
<blockquote><code>
md5 apache_1.3.x-<i>platform</i>.tar.gz >
apache_1.3.x-<i>platform</i>.tar.gz.md5
-<br>
+</code></blockquote>
+or if md5 is not present on your system
+<blockquote><code>
+openssl md5 apache_1.3.x-<i>platform</i>.tar.gz >
+ apache_1.3.x-<i>platform</i>.tar.gz.md5
+</code></blockquote>
+And create a PGP signature with
+<blockquote><code>
pgps -b -a <your-email-address> apache_1.3.x-<i>platform</i>.tar.gz
</code></blockquote>
or (pgp-2.6x):
<blockquote><code>pgp -sba apache_1.3.x-<i>platform</i>.tar.gz</code></blockquote>
-Make sure your PGP keys are already present in the <CODE>KEYS</CODE> file.
-
+Make sure your PGP keys are already present in the <CODE>KEYS</CODE> file. For completeness sake you should also sign the <code>apache_1.3.x-<i>platform</i>.README</code>
+file as well.
<P>
After you have successfully built the binary distribution, if you are
a core developer, you can upload the archive and README to the Apache
@@ -98,7 +105,9 @@
<blockquote><code>
scp apache_1.3.x-<i>platform</i>.* www.apache.org:/www/apache.org/dist/binaries/<i>platform</i>
</code></blockquote>
-
+Typically this should only be done after the web site has been update (see step
+30 in the <a href="how-to-release.html">release notes</a>) and if possible
+before the announcement.
<P>
You should then verify that the permissions on the file are 0664 (rw-rw-r--).
@@ -133,6 +142,7 @@
<H4>Darwin / Mac OS X</H4>
<UL>
<LI>powerpc-apple-rhapsody5.6: Wilfredo Sánchez
+<LI>powerpc-apple-darwin1.4: Dirk-Willem van Gulik
</UL>
<H4>DGUX</H4>
@@ -152,6 +162,7 @@
<LI>i386-whatever-freebsd2.2.8: Jim Jagielski
<LI>i386-whatever-freebsd3.0: Ken Coar
<LI>i686-whatever-freebsd3.1: Ralf S. Engelschall
+<LI>i686-whatever-freebsd4.x: Dirk-Willem van Gulik
</UL>
<H4>HPUX</H4>
@@ -198,6 +209,7 @@
<LI>sparc-sun-solaris2.5: Lars Eilebrecht
<LI>sparc-sun-solaris2.6: Lars Eilebrecht, Ralf S. Engelschall
<LI>sparc-sun-solaris2.7: Cliff Skolnick
+<LI>sparc-sun-solaris2.8: Dirk-Willem van Gulik
<LI>sparc-sun-sunos4.1.3_U1: Sameer Parekh
</UL>
1.74 +6 -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.73
retrieving revision 1.74
diff -u -r1.73 -r1.74
--- how-to-release.html 2001/06/28 00:07:09 1.73
+++ how-to-release.html 2001/10/11 22:47:41 1.74
@@ -430,6 +430,12 @@
<CODE><B>$ cvs update index.html</B></CODE>
<P>
<LI>At this point, the web-sites reflect the existance of the new release.
+ <p>
+ As it is going to be some 24hrs before any announcement goes out
+ (to make sure that the mirror's have at least a chance of grabbing
+ a copy) this is also the right time to mail dev@httpd.apache.org
+ and ask people to upload and move into position any
+ <a href="binaries.html">binaries</a> they have build and vetted.
</OL>
<P>