> To that end, I would suggest the following setup for the httpd-test
> repository
>
> httpd-test/test_framework
BTW, please call it perl_framework, or some witty name for it, since there
will be several test frameworks within this module. The eBuilt one is
called flood, but we can change that n
> > I suggest we simply create a new unix group for the test repository and
> > add everyone interested to that group. I do not want to play games on
> > the CVS module directory side because that will fail as soon as someone
> > without write access to both repositories tries a commit.
I talked
++1!
Can you take care of this?
Ryan
On Wed, 11 Jul 2001, Roy T. Fielding wrote:
> > The problem we have to solve, is that we have to allow all of the current
> > mod_perl developers to continue to have commit access to that code, and we
> > would like to remove any chance of code duplication.
> The problem we have to solve, is that we have to allow all of the current
> mod_perl developers to continue to have commit access to that code, and we
> would like to remove any chance of code duplication.
I suggest we simply create a new unix group for the test repository and
add everyone inter
Mod_perl has had a test framework for a long time. That same framework
can easily be used to create regression tests for Apache itself. I would
like to get that code base into the httpd-test CVS repository.
The problem we have to solve, is that we have to allow all of the current
mod_perl devel
