For those who have not been on the #squid-dev IRC channel lately I can
tell that the last weeks has been quite interesting.
The most significant news is that Doug Dixon (aka ganso on the IRC) has
volunteered for the role as Squid-3.0.PRE4 release manager. Expect a
message from him shortly
All
I aim to get Squid-3.0.PRE4 released in four to six weeks' time.
The list of bugs to be fixed in 3.0 is here:
http://tinyurl.com/f56qm
This includes bugs that were discovered in 2.5 but which still need
fixing in 3.0.
I am considering three options for setting the Squid-3.0.PRE4
lör 2006-05-06 klockan 12:08 +1200 skrev Doug Dixon:
Option 1 - severity based
We release PRE4 when all the criticals and blockers have been fixed.
Over optimistic. This is the quality level required for a RC/STABLE
release.
Option 2 - hand-picked
We hand pick a fixed list of bugs which we
Proposal:
Drop the Squid-3 patches page.
http://www.squid-cache.org/Version/v3/3.0/bugs/
It's not actively maintained and does not give much benefit to the
release process until we are ready to go to STABLE state I think.
If needed some of it's functionality can be resurrected from the
lör 2006-05-06 klockan 02:53 +0200 skrev Henrik Nordstrom:
Proposal:
Drop the Squid-3 patches page.
http://www.squid-cache.org/Version/v3/3.0/bugs/
Can't even type tonigt..
http://www.squid-cache.org/Versions/v3/3.0/bugs/
It's not actively maintained and does not give much benefit
On Sat, 2006-05-06 at 02:53 +0200, Henrik Nordstrom wrote:
Proposal:
Drop the Squid-3 patches page.
http://www.squid-cache.org/Version/v3/3.0/bugs/
It's not actively maintained and does not give much benefit to the
release process until we are ready to go to STABLE state I think.
On Sat, 2006-05-06 at 12:08 +1200, Doug Dixon wrote:
All
I aim to get Squid-3.0.PRE4 released in four to six weeks' time.
The list of bugs to be fixed in 3.0 is here:
http://tinyurl.com/f56qm
This includes bugs that were discovered in 2.5 but which still need
fixing in 3.0.
I am
Hi
A separate thread of activity will help get 3.0 firmed up:
1. Get the commit queue going better - there's lots of patches
submitted for 3.0 waiting to be reviewed/committed.
- review Target 3.0, Priority P1 bugs (which means a patch is ready
for review and commit) and commit to CVS
-
