From: "Chuck Murcko" <[EMAIL PROTECTED]>
Sent: Wednesday, April 18, 2001 12:14 AM
> I wanted to let things settle down a bit before popping this one, but
> with DSO, HTTP protocol, and multiprotocol changes on the way I think
> it's a good time. Plus the multiprotocol thread.
>
> There's actually been more accomplished with mod_proxy than I had hoped
> in this timeframe, thanks to Graham's and Victor's hard work.
>
> So, what do you think?
Ask the question this way instead, and see what your answer is [by the list's
original critera, yes, I'm +1 for reintegrating, but]...
Do we want to be bound to the new-httpd release cycle for getting fresh mod_proxy
capabilities out the door?
I'm asking this question for the multiprotocol front as well. Take the newish
mp3 module someone just authored for 1.3. Easy in 2.0. So the group 'accepts'
a code donation, and we have apache/mp3. When does that protocol code need to
be updated?
Since all these 'protocol' modules will start introducing new stability issues
(not in the core, but those modules themselves) do we start a flury of weekly
new-httpd releases to keep up, or do we start breaking these all into manageable
components, and reduce the frequency of releases for the apache core, letting
the modules (even things like https) float on their own release cycles against
the current (release-quality approved) core?
Not against a 'roll-up' release here, of core + release-quality branded modules,
but I'm suggesting we let these many (valuable!) sub-projects run at their own
paces.
Comments?
Bill
