Henrik Nordstrom wrote:
What is the status for 3.1?
At a minimum I would say it's about time for a 3.1.0.15 release,
collecting up what has been done so far.
I was planning it for this weekend, but have run out of time. Will be
next week.
Just holding out hope for that Solaris ICMP issue being resolved, then
we might be able to announce full Solaris support in this release.
The bigger question, what is blocking 3.1.1? (and moving 3.0 into
"previous releases")
Bugs...
3.0 bugs we should get fixed in 3.1: 1956, 2697, 2736, 2802.
** two of those are fails-to-build on Solaris.
3.1 bugs we need to fix still: 2811, 2619, 2604, 2311, 2790, 2753,
2706, 2685, 2640, 2583, 2581, 2395.
* 2811 is a concrete release blocker. The others highly desirable
polish fixes.
A bit of missing OS support if time permits. Sadly, I'm considering
those a potential write-off pre-release. The fixes for those will have
to be done post-release.
* OpenBSD and MacOSX split-stack support. For now IPv4-only.
* CVE2009-0801. Fix designed but not quite finished coding, and needs
some deep testing.
I'm guessing we have 4-8 weeks work there. Spread between us.
If we can settle on an SNMP table model and get bug 2811 closed soon I
think January is a real possibility for release date.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE7 or 3.0.STABLE20
Current Beta Squid 3.1.0.14
