Re: preX for squid-3.0?

On Mon, 2003-01-27 at 11:10, Henrik Nordstrom wrote:
> The auth fixes is waiting for you to bring them into CVS when you are
> happy with their state.

Yep. I think I'll bring them in tonight. I've had a couple of positive
feedbacks off-list.

> Lets try to keep the PRE cycle of 3.0 relatively short. Do not go into
> PRE unless you seriously expect that there won't be any more major
> changes or additions before STABLE.

Ok. Here's what I have pending as HEAD candidates:
* The ESI & surrogate control code. (Should be worked in with rproxy I
think - I'd like to see some of rproxy hit HEAD first).

There's plenty more that could be developed, and some things in the pipe
line (like refactoring the logging, the external logger, the custom
logger, delay pools for users ......)

But none of those are ready *now*. ESI Should be ready in < 1 month. And
once we declare PRE, I certainly won't be bringing any new features in,
only bugfixes.

> I have not paid close attention to 3.0 yet due to various reasons
> (kind of stuck in 2.5 at the moment) so I cannot say I have much of a
> opinion what 3.0.STABLE should have or what may be missing. I can
> however offer to bring over some of the basic aspects of rproxy to
> allow for more sane reverse proxy setups if wanted

It would be good to get some of the patches floating out there flushed
into 3. So yes, if your rproxy code is stable, lets bring it in.

Duane, any comment on 3.0? I think some of your -2 fixes still need to
be forward ported to 3.0 - are you planning on doing that?

Cheers,
Rob

-- 
GPG key available at: <http://users.bigpond.net.au/robertc/keys.txt>.