perl-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip M. Gollucci" <>
Subject Re: What happened with Apache2::Reload in mod_perl-2.0.4?
Date Mon, 21 Apr 2008 22:17:26 GMT
Hash: SHA1

Philippe M. Chiasson wrote:
| And as the latest Release Manager, I must say that having to release 3
| extra CPAN modules along with each mp2 releases is going to be a PITA.
Lots of svn:externals at play here, all perl/modperl/tags/* should have
externals that point to other perl/[project]/tags/* otherwise the tags
are useless after the fact.

Ideally, we should _shutter_ branch for releases and update the
externals there so that the generated tar.gz contains the correct code
for us to vote on.

I believe I documented it this way for httpd/apreq

See also, Apache-DBI, Apache-Reload, and Apache-SizeLimits
I believe all 4 have RELEASE notes for this we can copy from.

| The only negative is that if a change is made to say Apache-Test to fix a
| problem mod_perl needs/wants, it complicates things a little. I make the
| fix in A-T, making sure it fixes mod_perl's problem. If sure of that,
| I proceed to release A-T. Once released, I can now test mod_perl against
| this new A-T by locally changing the tag the svn:external is pointing to,
| and if it solves to problem and doesn't create new ones, checkin the new
| external definition.
Something like that.  Anyway you cut it, the other 3 have to be
'released' first if they have updates you need.

| Anyhting terribly obvious I am missing here ?
/me duck and hide

- --
- ------------------------------------------------------------------------
Philip M. Gollucci (
Senior System Admin - Riderway, Inc. /
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70  3F8C 75B8 8FFB DB9B 8C1C

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.

Version: GnuPG v2.0.8 (FreeBSD)
Comment: Using GnuPG with Mozilla -


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message