Matus UHLAR - fantomas wrote:
Hello,
On 17.03.08 10:18, Adrian Chadd wrote:
Just to summarise the discussion, both public and private.
* Squid-3 is receiving the bulk of the active core Squid developers' focus;
* Squid-2 won't be actively developed at the moment by anyone outside
of paid commercial work;
* I've been asked (and agreed at the moment) to not push any big changes to
Squid-2.
If your organisation relies on Squid-2 and you haven't any plans to migrate
to Squid-3, then there's a few options.
* Discuss migrating to Squid-3 with the Squid-3 developers, see what can be
done.
* Discuss commercial Squid-2 support/development with someone (eg Xenion/me).
* Migrate away from Squid to something else.
Obviously all of us would prefer that users wouldn't migrate away from
Squid in general, so if the migration to Squid-3 isn't on your TODO list
for whatever reason then its in your best interests -right now- to discuss
this out in the open.
I plan to migrate from Squie-2 to Squid-3 ASAP (got much other work to do)
because my current primary goal is ICAP which is available in squid-3.
Other, lower priority goals are
- caching of frequently used content, like youtube and possibly microsoft*
updates
- COSS storage
however in current situation even squid-2 is not a big win here, so I'm only
staying with squid-2 because of lack of time...
The biggest hitch here is that COSS in -3 still need a number of
stability fixes ported up from 2.6. Is there anything you could do to
encourage someone to come out of the woodwork and do the COSS fixes you
are going to need?
Amos
--
Please use Squid 2.6STABLE17+ or 3.0STABLE1+
There are serious security advisories out on all earlier releases.
