You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@perl.apache.org by Geoffrey Young <ge...@modperlcookbook.org> on 2003/10/22 21:48:11 UTC
[RELEASE CANDIDATE] Apache-Test-1.05-dev is available
a release candidate for Apache-Test 1.05 is now available.
http://perl.apache.org/~geoff/Apache-Test-1.05-dev.tar.gz
please take the time to excercise the candidate through all your existing
applications that use Apache-Test and report back any problems.
--Geoff
Changes since 1.04:
core scanning changes [Stas]
- speedup by not chdir'ing into subdirs
- an optional scanning of only t/ dir (used by TestSmoke)
- don't scan on win32, since it has no core files
in the autogenerated t/conf/modperl_inc.pl don't add the project/lib
directory, unless a special env var APACHE_TEST_LIVE_DEV is true. This
is because some projects change things in project/blib and pushing
project/lib on top of @INC, breaks the test suite for them [Stas]
TestRun was using httpd.pid file to ensure that the server is killed
before starting it, if the file existed. This was a problem on win32
platforms, where a process scheduler tries to re-use the pids that
were just freed, which may have killed a valid process which is not
even Apache.exe. So we try not to rely on that file, and if the server
wasn't properly stopped and still running, users will learn about
that, since the port will be busy, and Apache will fail to
start. Users have to kill it manually. TestSmoke is no longer using an
explicit kill `cat httpd.pid` to stop Apache, but delegates the
stopping procedure to TestRun [Steve Hay, Randy Kobes]
use IPC::Run3 in Apache::TestSmoke to run t/TEST commands,
so as t/SMOKE can be used on Win32 [Stas, Steve Hay, Randy Kobes]
place mod_perl-specific directives in <IfModule> containers
within httpd.conf, allowing the default server to start if
mod_perl isn't present. [Geoffrey Young]
fix t/request.t to get /index.html, instead of / since not everybody
uses mod_dir [Steve Piner <st...@marketview.co.nz>]
when testing whether Apache started as root and running under 'nobody'
or alike, will be able to -r/-w/-x in t/ use 'su' instead of 'sudo',
the latter is not available on all unix platforms. [Vivek Khera
<kh...@kcilink.com>]
in the Apache/test.pm nuke code s/PERLRUN/FULLPERL/ as older MakeMaker
doesn't have the PERLRUN target [Stas]
Apache 1.3 servers now run in standard prefork mode under
normal operation. single server mode (httpd -X) was replaced
with MaxClients set to 1 by default. [Geoffrey Young]
--Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [RELEASE CANDIDATE] Apache-Test-1.05-dev is available
Posted by David Wheeler <da...@kineticode.com>.
On Wednesday, October 22, 2003, at 04:13 PM, Stas Bekman wrote:
> We just try to walk the thin rope of balance and use our common sense
> to decide what should be noted and what note, often times noting to
> each other when we think that some change log is due or on the
> opposite useless.
Works for me.
Daviid
--
David Wheeler AIM: dwTheory
david@kineticode.com ICQ: 15726394
http://www.kineticode.com/ Yahoo!: dew7e
Jabber: Theory@jabber.org
Kineticode. Setting knowledge in motion.[sm]
Re: [RELEASE CANDIDATE] Apache-Test-1.05-dev is available
Posted by Stas Bekman <st...@stason.org>.
David Wheeler wrote:
> On Wednesday, October 22, 2003, at 02:30 PM, Stas Bekman wrote:
>
>> Seconded. We try to keep the Changes files to containing only
>> information about changes that help users decide whether they need to
>> upgrade to that newer version or not. If we log everything, the file
>> will become useless. We could just run cvs2lg to autogenerated a list
>> of all cvs changes.
Another important thing I forgot to mention is that when user upgrades to the
latest version and suddenly his stuff doesn't work as before, they will
probably first go to the Changes file and try to deduct what change could have
affected their case. Reading through 10 significact logs will help a user to
find that change, but she will most likely give up trying to wade through
hundreds of logs to find the relevant change.
> Well, that's a little different, and obviously quite useless.
>
> I try to track all changes in my Changes files because I think of it as
> a list of changes, not only those changes that are significant to those
> considering upgrading. And for the most part, they don't generally make
> it harder to evaluate.
It'd be very inconsistent if we log all changes from contributions, but only
selected ones from the core developers. And we do a lot of changes, most are
of very little interest to an end user.
>> There is another issue with acknowledging the contributions, but it's
>> probably not the reason to log those contributions in Changes. Perhaps
>> we need to start CONTRIBUTORS and simply list the names of
>> contributors there. We do change docs all the time, and trying to
>> track those changes is not simple and certainly doesn't belong to the
>> current Changes. Suggestions on how to improve that are certainly
>> welcome.
>
>
> CONTRIBUTORS is okay with me.
Cool. We shell have it then.
>> BTW, I did acknowledge that I've committed your patch, David, in reply
>> to your email with the patch.
>
>
> Yeah, I wasn't worried about that. I was just pointing out that if it
> was supposed to be a comprehensive list of changes, well, it wasn't. But
> if you guys prefer a different approach, well then never mind. :-)
We just try to walk the thin rope of balance and use our common sense to
decide what should be noted and what note, often times noting to each other
when we think that some change log is due or on the opposite useless.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: [RELEASE CANDIDATE] Apache-Test-1.05-dev is available
Posted by David Wheeler <da...@kineticode.com>.
On Wednesday, October 22, 2003, at 02:30 PM, Stas Bekman wrote:
> Seconded. We try to keep the Changes files to containing only
> information about changes that help users decide whether they need to
> upgrade to that newer version or not. If we log everything, the file
> will become useless. We could just run cvs2lg to autogenerated a list
> of all cvs changes.
Well, that's a little different, and obviously quite useless.
I try to track all changes in my Changes files because I think of it as
a list of changes, not only those changes that are significant to those
considering upgrading. And for the most part, they don't generally make
it harder to evaluate.
> There is another issue with acknowledging the contributions, but it's
> probably not the reason to log those contributions in Changes. Perhaps
> we need to start CONTRIBUTORS and simply list the names of
> contributors there. We do change docs all the time, and trying to
> track those changes is not simple and certainly doesn't belong to the
> current Changes. Suggestions on how to improve that are certainly
> welcome.
CONTRIBUTORS is okay with me.
> BTW, I did acknowledge that I've committed your patch, David, in reply
> to your email with the patch.
Yeah, I wasn't worried about that. I was just pointing out that if it
was supposed to be a comprehensive list of changes, well, it wasn't.
But if you guys prefer a different approach, well then never mind. :-)
Regards,
David
--
David Wheeler AIM: dwTheory
david@kineticode.com ICQ: 15726394
http://www.kineticode.com/ Yahoo!: dew7e
Jabber: Theory@jabber.org
Kineticode. Setting knowledge in motion.[sm]
Re: [RELEASE CANDIDATE] Apache-Test-1.05-dev is available
Posted by Stas Bekman <st...@stason.org>.
Geoffrey Young wrote:
>
>
> David Wheeler wrote:
[...]
>> I think that this release contains my fixes to the TestRequest::POST
>> documentation, too. Or was that in 1.04?
>
>
> do you mean this?
>
> http://cvs.apache.org/viewcvs.cgi/httpd-test/perl-framework/Apache-Test/lib/Apache/TestRequest.pm.diff?r1=1.87&r2=1.88
>
>
> this was added after 1.04.
>
> I guess we are inconsistent in logging doc changes in Changes.
>
> personally, I think the Changes file is most useful if it logs only
> functionality changes. but there are other documentation issues
> mentioned there currently, so if you'd like I'll insert that into
> Changes in (around) the appropriate place chronologically.
Seconded. We try to keep the Changes files to containing only information
about changes that help users decide whether they need to upgrade to that
newer version or not. If we log everything, the file will become useless. We
could just run cvs2lg to autogenerated a list of all cvs changes.
There is another issue with acknowledging the contributions, but it's probably
not the reason to log those contributions in Changes. Perhaps we need to start
CONTRIBUTORS and simply list the names of contributors there. We do change
docs all the time, and trying to track those changes is not simple and
certainly doesn't belong to the current Changes. Suggestions on how to improve
that are certainly welcome.
BTW, I did acknowledge that I've committed your patch, David, in reply to your
email with the patch.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: [RELEASE CANDIDATE] Apache-Test-1.05-dev is available
Posted by David Wheeler <da...@kineticode.com>.
On Wednesday, October 22, 2003, at 02:26 PM, Geoffrey Young wrote:
> I forgot to add that I certainly don't mean to belittle your
> contributions here - you've done lots of work on the docs and added
> lots of value. I even mentioned you by name at my OSCon talk :)
Awe, shucks. I wasn't feeling belittled, BTW.
> I'll give it some thought, look over Changes more closely, and then
> probably add it in :)
Okay.
David
--
David Wheeler AIM: dwTheory
david@kineticode.com ICQ: 15726394
http://www.kineticode.com/ Yahoo!: dew7e
Jabber: Theory@jabber.org
Kineticode. Setting knowledge in motion.[sm]
Re: [RELEASE CANDIDATE] Apache-Test-1.05-dev is available
Posted by Geoffrey Young <ge...@modperlcookbook.org>.
>> I guess we are inconsistent in logging doc changes in Changes.
>>
>> personally, I think the Changes file is most useful if it logs only
>> functionality changes. but there are other documentation issues
>> mentioned there currently, so if you'd like I'll insert that into
>> Changes in (around) the appropriate place chronologically.
>
>
> Oh. Up to you guys; I thought stuff like that was always noted.
I forgot to add that I certainly don't mean to belittle your contributions
here - you've done lots of work on the docs and added lots of value. I even
mentioned you by name at my OSCon talk :)
I'll give it some thought, look over Changes more closely, and then probably
add it in :)
--Geoff
Re: [RELEASE CANDIDATE] Apache-Test-1.05-dev is available
Posted by David Wheeler <da...@kineticode.com>.
On Wednesday, October 22, 2003, at 02:17 PM, Geoffrey Young wrote:
> do you mean this?
>
> http://cvs.apache.org/viewcvs.cgi/httpd-test/perl-framework/Apache-
> Test/lib/Apache/TestRequest.pm.diff?r1=1.87&r2=1.88
Yes.
> this was added after 1.04.
>
> I guess we are inconsistent in logging doc changes in Changes.
>
> personally, I think the Changes file is most useful if it logs only
> functionality changes. but there are other documentation issues
> mentioned there currently, so if you'd like I'll insert that into
> Changes in (around) the appropriate place chronologically.
Oh. Up to you guys; I thought stuff like that was always noted.
Cheers,
David
--
David Wheeler AIM: dwTheory
david@kineticode.com ICQ: 15726394
http://www.kineticode.com/ Yahoo!: dew7e
Jabber: Theory@jabber.org
Kineticode. Setting knowledge in motion.[sm]
Re: [RELEASE CANDIDATE] Apache-Test-1.05-dev is available
Posted by Geoffrey Young <ge...@modperlcookbook.org>.
David Wheeler wrote:
> On Wednesday, October 22, 2003, at 12:48 PM, Geoffrey Young wrote:
>
>> a release candidate for Apache-Test 1.05 is now available.
>>
>> http://perl.apache.org/~geoff/Apache-Test-1.05-dev.tar.gz
>>
>> please take the time to excercise the candidate through all your
>> existing applications that use Apache-Test and report back any problems.
>
>
> I think that this release contains my fixes to the TestRequest::POST
> documentation, too. Or was that in 1.04?
do you mean this?
http://cvs.apache.org/viewcvs.cgi/httpd-test/perl-framework/Apache-Test/lib/Apache/TestRequest.pm.diff?r1=1.87&r2=1.88
this was added after 1.04.
I guess we are inconsistent in logging doc changes in Changes.
personally, I think the Changes file is most useful if it logs only
functionality changes. but there are other documentation issues mentioned
there currently, so if you'd like I'll insert that into Changes in (around)
the appropriate place chronologically.
--Geoff
Re: [RELEASE CANDIDATE] Apache-Test-1.05-dev is available
Posted by David Wheeler <da...@kineticode.com>.
On Wednesday, October 22, 2003, at 12:48 PM, Geoffrey Young wrote:
> a release candidate for Apache-Test 1.05 is now available.
>
> http://perl.apache.org/~geoff/Apache-Test-1.05-dev.tar.gz
>
> please take the time to excercise the candidate through all your
> existing applications that use Apache-Test and report back any
> problems.
I think that this release contains my fixes to the TestRequest::POST
documentation, too. Or was that in 1.04?
David
--
David Wheeler AIM: dwTheory
david@kineticode.com ICQ: 15726394
http://www.kineticode.com/ Yahoo!: dew7e
Jabber: Theory@jabber.org
Kineticode. Setting knowledge in motion.[sm]