You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by "Ralf S. Engelschall" <rs...@engelschall.com> on 1999/12/16 09:26:37 UTC
Re: cvs commit: apache-1.3 STATUS
In article <19...@hyperreal.org> you wrote:
> [...]
> * Ralf's [PATCH] to add EAPI (ctx, hook, mm, etc.) to the base package
> Message-ID: <19...@engelschall.com>
> - Status: Jim -1 (alternatives?), Mark +1, Dean +1, BenH +1,
> + Status: Mark +1, Dean +1, BenH +1,
> Randy +1 (please choose name other than "hook")
> Doug +1 on concept (untested), Lars +1 on concept,
> - Martin +1 (untested), Ken -1 for 1.3.7 (too controversial,
> - esp. w/KEAPI offered as well), Fred +1
> + Martin +1 (untested), Fred +1,
> + Jim ---0 (I really don't think it makes sense to
> + add this right now. If we do, then we want a "long"
> + beta period so that other packages that need to
> + patch the official source code have plenty of time
> + to make the required changes)
<grin> Once again: First, there is only one package which will have this
problem (Ben's Apache-SSL) and it will have it only _ONCE_, second one
doesn't need plenty of time to make the required changes (it's a matter
of one afternoon), third even Ben said it's not such a great problem
for him and forth, if all should fail for Apache-SSL I also volunteered
to help out, too. Additionally EAPI for non-EAPI users cannot break
anything, because the whole stuff is 100% #ifdef'ed and fully optional
and disabled per default. So I'm really wondering about the repeated
strong arguments for such a harmless issue... hmm.... very confusing.
Ralf S. Engelschall
rse@engelschall.com
www.engelschall.com
Re: cvs commit: apache-1.3 STATUS
Posted by Peter Galbavy <Pe...@knowledge.com>.
On Thu, Dec 16, 1999 at 09:00:03AM -0500, Jim Jagielski wrote:
> I propose that 1.3.10 be released without EAPI and IPv6. The first
> patches to 1.3.11-dev be these 2 patches (EAPI is _enabled_). After
> a adequate beta period, we release 1.3.11. I don't think we should
> hold off on 1.3.10.
For what it's worth, not being a member of the development group,
I agree with Jim's approach. Use 1.3.10 to fix issues from 1.3.9
and then immediately set the goals for 1.3.11 to include the new
features.
Regards
--
Peter Galbavy
Knowledge Matters Ltd
http://www.knowledge.com/