Kinkie pointed out Linus Torvalds blog today to the rest of us here working on Squid. As the release maintainer for Squid-3 this year I kind of agree, its a sad time to cutting a new version. For me its more of a reflection that for all the high hopes we have of this new release, we had the same or similar hopes of the earlier one. Just 12 months ago now.
On that sad note, yes its finally happened. 3.0 has aged into a full blown stable package. Most of a month and no new bugs. Perfect time for something shiny and new for the neo-tech fanclub. And so with that for an intro we are gone for 3.1 !
This release has gained from the experiences of 3.0 and 2.6, starting from a much more stable base of code than the initial. 3.0 had a long period of years with few active developers, an interminably long period of testing releases, and in hindsight a premature birth.
Alongside the code this release has a wider collaboration with active users. For the first time in many years we held a Developer meeting that included Users. We who were there certainly took in a lot of feedback from all sides. I hope those users who talked to us can see in this release that their comments, even those made in passing, have been listened to and worked on.
The small comment from one user when asked what their biggest itch with squid was “we don’t like these being called STABLE, when its obvious they are not.” has led to the most notable change made to 3.1. That comment and similar feelings by others lead us into discussions on the release naming and numbering. From which we have produced – 126.96.36.199 – the second milestone point of the branch we are calling 3.1. Where the developers have everything done and working for us.
no more DEVEL, PRE, or RC, no more premature labels guessing when things might be STABLE. Just 188.8.131.52. Further testing from the rest of you will show whether anyone can consider it stable, unstable, usable or as buggy as raw earth.
From the developers; We use it. We love it. Try it, and see for yourselves.
Some of the stuff you will find there is;
- a lot of small changes aimed towards easier use and configuration (three cheers to those who nagged long an hard for this).
- a lot of network RFC compliance extensions, making 3.1 much more capable of meeting modern network needs. The future still holds improvements, but 3.1 is definitely better in many respects than everything that came before.
- a lot of things to make Squid a better experience for your own users. More seamless network recovery tricks than ever before. We have even tagged along behind the international localization bandwagon in our own way to make the errors squid does have to show both pretty and readable.
Sadly, careful readers will notice a section of the Release Notes labeled “Regressions against 2.7″. Yes, those of you who moved to 2.7 because you needed some brand new feature there may still have trouble migrating up to 3.1. What we have done is to port as many of the 2.6 features and fixes as we could. A few did not make it in time, but will be coming in 3.2, alongside the features added as experimental in 2.7.
On the overview:
- 2.5 has disappeared over the horizon into the long dark night of obsoletion.
- 2.6 is itself officially aging out now. Supported, but the developer first response is “can you try something newer?”.
- 2.7 is being maintained for the few extremely high-performance accelerator setups. But in general the Squid-2 sequence is aging out for us developers.
- 3.0 has reached a point of stability, though not fully-featured.
- 3.1 is available for testing as the next step up. You should be planning to migrate up to 3.1 or later release.
If there are any features holding you to Squid-2, or even an issues you find with testing Squid-3 speak up, we rely on your input to choose the most needed features for porting.
Thank you all, and enjoy your use of Squid 3.1