Greg Stein wrote:
> Even better, the proxy guys should say "okay. we have verified that our
> stuff works with the 2.0.18 tarball, so let's release an apache+proxy
> tarball."
Really yuck for the end user.
There should be just one archive out there. There is no point in
releasing an archive with A in it, then something with A+B - it's a
complete waste of time.
> How was FirstBill to know whether proxy should have been included
> or not? Was it stable and did it work against 2.0.18? No... he doesn't know
> that.
Then lets finalise the decision and they will know.
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
- Tagging Apache 2.0 for beta candidate Bill Stoddard
- Re: Tagging Apache 2.0 for beta candidate Graham Leggett
- Re: Tagging Apache 2.0 for beta candidate William A. Rowe, Jr.
- Re: Tagging Apache 2.0 for beta candidat... rbb
- Re: Tagging Apache 2.0 for beta candidat... Bill Stoddard
- Re: Tagging Apache 2.0 for beta cand... William A. Rowe, Jr.
- Re: Tagging Apache 2.0 for beta... Bill Stoddard
- Re: Tagging Apache 2.0 for ... Bill Stoddard
- Re: Tagging Apache 2.0 ... Roy T. Fielding
- Re: Tagging Apache 2.0 for ... Greg Stein
- Re: Tagging Apache 2.0 ... Graham Leggett
- Re: Tagging Apache 2.0 ... Greg Stein
- Re: Tagging Apache 2.0 ... Graham Leggett
- Re: Tagging Apache 2.0 for ... William A. Rowe, Jr.
- Re: Tagging Apache 2.0 ... William A. Rowe, Jr.
- Re: Tagging Apache 2.0 ... Greg Stein
- Re: Tagging Apache 2.0 ... Graham Leggett
- Re: Tagging Apache 2.0 for ... Graham Leggett
- .Re: Tagging Apache 2.0 for beta candidate William A. Rowe, Jr.
- Re: Tagging Apache 2.0 for beta candidate Jeff Trawick
S/MIME Cryptographic Signature