On Wed, 2008-02-27 at 14:30 +1100, Mark Nottingham wrote: > > * Besides the availability of *CAP and ESI -- which are very > specialised, and of interest only to a subset of Squid users -- is > there any user-visible benefit to switching to -3? class 4 delay pools, some request tagging stuff too IIRC. > * What do the developers consider to be a success metric for -3? > I.e., when will maintenance on -2 stop? I think of this as apache 1.x and 2.x - maintenance on -2 won't come to a hard stop until -3 (or -4, or whatever) is a solid viable upgrade across the board. > * Until that time, what is the development philosophy for > Squid-2? > Will it be only maintained, or will new features be added / rewrites > be done as (possibly sponsored) resources are available? Looking at > <http://wiki.squid-cache.org/RoadMap/Squid2 > >, it seems to be the latter; is that the correct interpretation? Folk will scratch their own itches - thats open source for you. I know I'd really prefer it if features being added are *primarily* added to -3 - I'm totally supportive of backporting to -2, but would rather see it as a backporting process rather than a forward porting process. > * If that success metric is not reached, what is the contingency > plan? I don't know what you really mean here. Squid isn't a corporate entity with a monetary either-or marketing/funding style problem. > * How will these answers change if a substantial number of users > willingfully choose to stay on -2 (and not just because they neglect > to update their software)? Well, I'd hope that at the minimum those users would file bugs on the things about -3 that keep them on -2, so that developers can fix them :). > > Also, a few questions for -users: > > * Who is using -3 in production now? How are you using it (load, > use case, etc.) and what are your experiences? I use -3, have for ages. But its trivial home-site accelerating and browsing, so entirely uninteresting at the scope of yahoo :). -Rob -- GPG key available at: <http://www.robertcollins.net/keys.txt>.
Attachment:
signature.asc
Description: This is a digitally signed message part
