I'd really like to see some of the features in a release, and am happy to help where I can.
On 21/06/2011, at 9:08 AM, Henrik Nordström wrote: > With the release of Squid-3.2 it's about time we drop Squid-2.7 as a > supported release. Maintenance of Squid-2 have already fallen way > behind, not receiving anywhere close to the attention deserved for a > "supported release" with all currently active developers mainly focusing > on Squid-3. > > Squid-3 have in the meantime also gained a lot of interesting > functionality, both ported from Squid-2 and new functionality, > considerably closing the upgrade feature gap. There is still some > feature gap left, but it is getting smaller and smaller. > > One way to see this is that if you or someone you know is stuck in > Squid-2.7 for some reason then it's about time to look into solving that > now. In reality that should have been done years ago. > > In practice it does not mean that much as maintenance of Squid-2.7 is > already practically stopped with last release over a year ago. Partly > because there isn't very much left to fix in the release, but also > because there simply isn't any project resources actively working on > Squid-2 maintenance. > > There is some bug fixes pending in the Squid-2 merge queue, sufficient > to compose a final release, but if you know of any more Squid-2 bugs > that really should be fixed please speak up now. > > Then there is some feature stuff in Squid-2.HEAD, but I think these will > remain there. I do not see sufficient momentum for branching a Squid-2.8 > release. > > See http://www.squid-cache.org/Versions/v2/2.HEAD/changesets/merge.html > for lists of both pending merges to 2.7 and 2.HEAD specific features. > > So at the moment it looks like there will be one final Squid-2.7 release > collecting some pending bug fixes, after which maintenance of the > Squid-2 tree will cease completely, enabling the project to focus > entirely on Squid-3. > > Regards > Henrik > -- Mark Nottingham m...@yahoo-inc.com
