Re: squid3 future directory structure
On Wed, Feb 27, 2008 at 4:37 AM, Alex Rousskov [EMAIL PROTECTED] wrote: On Wed, 2008-02-27 at 11:33 +1100, Robert Collins wrote: So you would recommend something like http/request_method.cc and acl/request_header_strategy.h I prefer not to use camelcase when it comes to filenames, so count my vote for this proposal. -- /kinkie
Re: Time for squid 3.0 STABLE2 ?
Henrik Nordström wrote: tis 2008-02-19 klockan 23:00 +0100 skrev Guido Serassio: Hi, What about to release squid 3.0 STABLE2 ? Probably, even if I prefer to fix forwarding of large response headers first.. but it should not be a blocker for STABLE2.. I think that there are many patches already applied to HEAD-3 that could be applied also to SQUID_3_0. Certainly. Regards Henrik Henrik, could you check your patch 11467 and port it to 3.0 please? It's not applying cleanly. Amos -- Please use Squid 2.6STABLE17+ or 3.0STABLE1+ There are serious security advisories out on all earlier releases.
Re: Time for squid 3.0 STABLE2 ?
Just a few issues remaining before 3.0.STABLE-2. * patch 11467 back-porting. * Close more bugs? http://www.squid-cache.org/bugs/show_bug.cgi?id=2127 http://www.squid-cache.org/bugs/show_bug.cgi?id=2124 why is this not 2.6?? http://www.squid-cache.org/bugs/show_bug.cgi?id=2138 * Build and tests on as many OS as possible. (branch: SQUID_3_0) I am running the tests I use on Debian/Ubuntu already. Could the rest of you please jump in for any OS you have tests for or even just compiling on. * CVS branching? checkpoint?. Will need another How-To here I think Henrik. * Release announcement. Amos -- Please use Squid 2.6STABLE17+ or 3.0STABLE1+ There are serious security advisories out on all earlier releases.
Squid conference
On Wed, 2008-02-27 at 15:20 +1100, Mark Nottingham wrote: Is this going to be a semi-regular event? I'd be interested in participating in the future, but need more lead time to arrange travel... If enough folks want to meet, we should organize a Squid Conference. A conference would allow users, vendors, and developers to discuss all matters related to the Squid project in a high-bandwidth environment. We can do hands-on training sessions and even vendor exhibits if enough people sign up for the event. A conference will require planning in advance, of course. If you are potentially interested, please post here or email me personally. Please name two or three cities where you would prefer to meet and mention any scheduling preferences you may have. Thank you, Alex.
Re: Time for squid 3.0 STABLE2 ?
On Thu, 2008-02-28 at 01:04 +1300, Amos Jeffries wrote: Just a few issues remaining before 3.0.STABLE-2. * patch 11467 back-porting. cd English ls ERR_* ../list * Close more bugs? http://www.squid-cache.org/bugs/show_bug.cgi?id=2127 http://www.squid-cache.org/bugs/show_bug.cgi?id=2124 why is this not 2.6?? http://www.squid-cache.org/bugs/show_bug.cgi?id=2138 * Build and tests on as many OS as possible. (branch: SQUID_3_0) I am running the tests I use on Debian/Ubuntu already. Could the rest of you please jump in for any OS you have tests for or even just compiling on. * CVS branching? checkpoint?. Will need another How-To here I think Henrik. * Release announcement. Amos
Re: Time for squid 3.0 STABLE2 ?
On Thu, 2008-02-28 at 01:04 +1300, Amos Jeffries wrote: Just a few issues remaining before 3.0.STABLE-2. * patch 11467 back-porting. cd English ls ERR_* ../list * Close more bugs? http://www.squid-cache.org/bugs/show_bug.cgi?id=2127 Is closed and verified by the reporter. http://www.squid-cache.org/bugs/show_bug.cgi?id=2124 Done. why is this not 2.6?? http://www.squid-cache.org/bugs/show_bug.cgi?id=2138 Don't know. * CVS branching? checkpoint?. Will need another How-To here I think Henrik.t update releasenotes and changelog. login on squid/cache.org and - get an up to date checkout of the tree cvs up -d -P - make sure the version in configure.in is correct - ./bootstrap.sh - cvs commit - cvs tag SQUID_3_0_STABLE2 - ./mkrelease.sh squid-3.0.STABLE2 /server/httpd/htdocs/squid-cache.org/Versions/v3/3.0/ (i think, verify the path) this should give you a suitable tarball in the website. download that, and the previous release and signature as well. verify the signature of the previous release make a diff between the two, and audit that diff to verify that the changes looks right. sign the new release and diff. upload the diff and signatures to the 3.0 folder on the web server. go to the 3.0 web folder co -l index.tmpl edit index.tmpl, moving the previous release down to older stable releases and the new as current stable release. ./make.sh verify that it got published right. copy the tarballs, diff, release notes and signatures to the ftp area. send announce
Re: Time for squid 3.0 STABLE2 ?
Hi all, Henrik Nordstrom wrote: On Thu, 2008-02-28 at 01:04 +1300, Amos Jeffries wrote: * Close more bugs? http://www.squid-cache.org/bugs/show_bug.cgi?id=2127 Is closed and verified by the reporter. About bug 2127, my understanding is that there are references about two bugs here. I am not sure, but I think the original bug reported here did not solved and still exists Regards, Christos
Re: Time for squid 3.0 STABLE2 ?
On Thu, 2008-02-28 at 01:04 +1300, Amos Jeffries wrote: Just a few issues remaining before 3.0.STABLE-2. snip done * Close more bugs? Booger: stub time| COSS block-size = 512 bytes stub time| COSS largest file offset = -1 KB stub time| COSS cache_dir size = 102400 KB stub time| Fatal: COSS cache_dir size exceeds largest offset .FAIL: tests/testCoss why is this not 2.6?? http://www.squid-cache.org/bugs/show_bug.cgi?id=2138 Don't know. * CVS branching? checkpoint?. Will need another How-To here I think Henrik.t update releasenotes and changelog. done. remainder pending the make-check failure. login on squid/cache.org and - get an up to date checkout of the tree cvs up -d -P - make sure the version in configure.in is correct - ./bootstrap.sh - cvs commit - cvs tag SQUID_3_0_STABLE2 - ./mkrelease.sh squid-3.0.STABLE2 /server/httpd/htdocs/squid-cache.org/Versions/v3/3.0/ (i think, verify the path) this should give you a suitable tarball in the website. download that, and the previous release and signature as well. verify the signature of the previous release make a diff between the two, and audit that diff to verify that the changes looks right. sign the new release and diff. upload the diff and signatures to the 3.0 folder on the web server. go to the 3.0 web folder co -l index.tmpl edit index.tmpl, moving the previous release down to older stable releases and the new as current stable release. ./make.sh verify that it got published right. copy the tarballs, diff, release notes and signatures to the ftp area. send announce
Re: Time for squid 3.0 STABLE2 ?
On Thu, Feb 28, 2008, Amos Jeffries wrote: * Close more bugs? Booger: stub time| COSS block-size = 512 bytes stub time| COSS largest file offset = -1 KB stub time| COSS cache_dir size = 102400 KB stub time| Fatal: COSS cache_dir size exceeds largest offset .FAIL: tests/testCoss I'd suggest just disabling COSS in -3 until someone ports over the changes or replaces it with something better. It really is actually very broken for even light production use. Adrian
