Re: How does it work?

On Thu, 13 May 2004, Mati wrote:

> I was wondering if there are some tools that you use to test squid?

web-polygraph is quite good, but it focuses on performance not advanced
functionality.

> The first being that we are finishing with ETag+Vary support and want to be
> sure that we haven't messed any existing functionalities up...
>
> The second reason is that to test our code we developed a tool
> for testing squids behaviour and wonder if you would want to use it.

Very interesting. Please eloberate on the capabilities of this tool.

We really need something useful to build a functional test suite for Squid
for the very exact same reasons you outline.

> I also wondered how the code is merged to HEAD?

By the developer asking to have the code merged into HEAD. There is then a
short public review of the implementation and if deemed suitable it
usually gets merged after a few interactions like "why have you done this
this way? Isn't it better to do it like this?" or "please change this
part because ..."

The earlier you involve others in your developments the faster the final
review process is. But we do request that a feature is reasonably finished
and tested before merged.

There is also some minor things complicating matters such as HEAD
currently being in feature freeze to allow for Squid-3.0 to stabilize, but
this (the feature freeze) is not something you have to worry about.

> I mean how the decision whether to include new code or not is made...

Mostly by discussion here on squid-dev. All that is needed is to get one
of the core developers convinced that your solution is good, and none of
the other strongly oppose inclusion.

Regards
Henrik
Received on Thu May 13 2004 - 04:06:17 MDT