Re: Squid3 HEAD commit order after v3.0

From: Amos Jeffries <squid3@dont-contact.us>
Date: Tue, 27 Nov 2007 10:30:20 +1300 (NZDT)

> On Thu, 2007-11-22 at 22:02 +0100, Rafael Martinez (Squid development)
> wrote:
>
>> Consider including SNMP support for IPv6....
>> It's almost done !!
>>
>> Ony a few tests with IPv6 cache peers !
>>
>> Transport is now on UDP/IPv6 and UDP/IPv4 !
>
> I believe IPv6 patch would be the first big change committed to Squid3
> HEAD once v3.0 is branched out. My understanding is that it will include
> SNMP and all other IPv6-related changes. Please correct me if I am
> wrong.

Yes. As soon as the branch is made I will start the ipv6 merge in this order:
 - new independant files; IPAddress, getaddrinfo, etc. That support the
later of the pieces.
  Anything ready that does not alter IP handling code can go in at the
same time. There are a dozen or so files I think for that. Maybe 3-4
days at most.
 ** by anything not touching IP, I'm thinking store, buffer, header,
cleanups etc.

 - then after a re-sync with HEAD to drop the critical core patch size.
The big one will go in.

>
> The second big change may be the async call code that Christos Tsantilas
> is working on. A lot of core code will be touched by the async-calls
> branch so the sooner we get those changes in the better.

This may result in more cleanup for me.

>
> SSL Bump and eCAP support should also be committed relatively soon, but
> they do not affect a lot of core code so there is less pressure and the
> order is less important for them.

SSLBump will need a refactoring after the IPAddress gets merged. As the
Config.* updates will likely clash. I have not followed eCAP closely, but
I don't think it will.

I am thinking an IPv6 PRE1 dec/jan. SSLBump seems to be good enough to
join it.

If you think eCAP is stable enough it might go in PRE1, but the async work
still seems to be very volatile. I think that should be timelined for PRE2
feb/mar after some more testing as it is now.

By then we will be closing off the 'new' features for 3.1RC1 and be able
to timeline the rest of the PRE with those features.

Thanks
Amos
Received on Mon Nov 26 2007 - 14:30:23 MST

This archive was generated by hypermail pre-2.1.9 : Sat Dec 01 2007 - 12:00:05 MST