Re: squid-3 vs 2.6

lör 2006-06-24 klockan 18:57 +0200 skrev Guido Serassio:

> Here I agree about the reasons, but I am doubtful about a 3.0 with
> not all the 2.6 features:

It's a simple matter or project priorities. With no doubt the absolutely
highest priority for Squid-3 must be get a stable release out as soon as
possible. The more new features added the longer this will take.

> why someone will "downgrade" its proxy ?

Why not? And if they don't want to they have the choice of making sure
they don't need to.

Why is Squid-3 completely outside it's original release plan, and still
no-one knowing when it's reasonable to expect a stable release?

> Just for example: all my customers are waiting for connection pinning
> with open arms ....

Then I am pretty sure at least one of them is willing to sponsor the
development and bug fixing required to get that feature in squid-3,
making it available as a patch to the Squid-3.0 release early on, and
then merged into 3.1.

Or if you prefer spending your time implementing the connection pinning
for 3.0 instead of fixing bugs then you are very welcome to. When
complete and tested in production it's a candidate for merging. If good
it may make it into 3.0, else 3.1.

> I remember the proposal when 2.6 work was announced:
>
> 1) 3.0 initially mainly for high end reverse proxies (ICAP & ESI) and
> 2.6 for forward proxies
> 2) 3.1 for both usage with all features.

> It seems to me a good compromise for a customer.

I am not sure even 3.1 will be 100% feature complete. I don't think we
as a team can bind to that promise as it's very dependent on what other
tasks each of us take for the 3.1 release.

The most important is that we make progress. If this means some features
is deferred so be it. There is no sponsor behind this project who work
on such generic scale as "feature complete". Customers mostly pay for
what they need, i.e. bug fixing of the issues they run into or features
they need. Outside that we can not force anything on anyone else than
yourself.

 * Any release plans depending on forcing something to get done is a
risky one.
 * Open Source development works by interest, not force.
 * The single thing holding Squid-3 back is the fact that it's not
stable. Until Squid-3 is stable it's very hard to shift development over
there, and even harder to draw customer attention.

Regards
Henrik