perl-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stas Bekman <s...@stason.org>
Subject Re: nuking old mod_perls before installing unstable
Date Tue, 22 Mar 2005 15:38:31 GMT
Stas Bekman wrote:
> Geoffrey Young wrote:
> [...]
> 
>> basically, my position is that mod_perl is not at 2.0 yet, so until it 
>> does
>> the entire API is up for grabs. 
> 
> 
> Your (current pmc's) position completely disregards the fact that when 
> we announced the first RC1 we said that the API is *frozen* and very 
> minor bug fixes may affect the API to a very minimum. We have given 
> people the green light to port their projects to mp2, promising that 
> only minor changes might be required before the gold 2.0 goes out.
> 
> What you are proposing is a blow in the face not only to the users but 
> to the developer's in first place, completely undermining any words that 
> were said to the users before.
> 
> This is immature.

It didn't take too long to see the surprised comments from developers:

-------- Original Message --------
Subject: Re: Many perl glue problems
Date: Tue, 22 Mar 2005 12:59:09 +0100
From: Max Kellermann <max@duempel.org>
To: Markus Wichitill <mawic@gmx.de>
CC: apreq-dev@httpd.apache.org
References: <20050322085314.GB9732@roonstrasse.net> <423FFC4A.4080101@gmx.de>

On 2005/03/22 12:06, Markus Wichitill <mawic@gmx.de> wrote:
 > AFAICT there's only one unstable apreq branch with both the multi-env
 > stuff and the Apache2:: namespace change, for which you'd need the
 > unstable mod_perl branch, too.
 >
 > 
http://svn.apache.org/repos/asf/perl/modperl/branches/apache2-rename-unstable

Thanks, that solved my problem. All tests pass.

So they're changing the API after they published a release
candidate.. strange.

Max



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org


Mime
View raw message