4 Sep 2003 05:46
[STATUS] (apr-serf) Wed Sep 3 23:46:24 EDT 2003
Rodent of Unusual Size <Ken.Coar <at> Golux.Com>
2003-09-04 03:46:27 GMT
2003-09-04 03:46:27 GMT
APR-SERF STATUS: -*-text-*- Last modified at [$Date: 2002/07/01 15:51:57 $] Release: RELEASE SHOWSTOPPERS: We need code. This project's goal is to create an http client library. * web pages (go to apr-site) * decide on layout of the repository (e.g. subdirs) Greg thinks: prolly the following: /build, /include, /docs, /test, /core, and some for high-level items (maybe /filters and /utils) Justin says: Fine with me except /core can't be used as autoconf trounces this directory via rm -rf - how about /base? * set up config/build structure based on apr-util (take this opportunity to simplify again; hopefully to fold these simplifications back into apr(-util)) * release scripts (in /build) (and a how-to-release.txt in docs/) RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
--Cliff
---------- Forwarded message ----------
Received: from config.mail.Virginia.EDU (config.mail.Virginia.EDU
[128.143.2.245])
by ares.cs.Virginia.EDU (8.12.9/8.12.8/UVACS-2003031900) with ESMTP
id h87JxtqU027016
for <jcw5q <at> cs.Virginia.EDU>; Sun, 7 Sep 2003 15:59:55 -0400 (EDT)
Received: from cgatepro-3.mail.virginia.edu (guppy.mail.Virginia.EDU
[128.143.2.218])
by config.mail.Virginia.EDU (8.9.3p2/8.9.3) with ESMTP id PAA18216
for <jcw5q%cs.virginia.edu <at> cmsrelay.mail.virginia.edu>; Sun,
7 Sep 2003 15:59:55 -0400 (EDT)
Received: from <jcw5q <at> cgatepro-3.mail.virginia.edu>
by cgatepro-3.mail.virginia.edu (CommuniGate Pro RULES 4.1)
with RULES id 55935400; Sun, 07 Sep 2003 15:59:55 -0400
RSS Feed