Re: RC5 really broke some stuff

[prev] [thread] [next] [Date index for 2005/04/21]

Its pretty well documented everywhere -- including the  announcement 
and install instructions

libapreq does not work right yet.  if you're dealing with production or 
stability sensitive stuff, i'd suggest keeping a copy of RC4 running 
and development on that release, then reading the migration 
instructions to the new API once everything is sorted out.

================


the mod_perl development team is pleased to announce the latest version 
of
mod_perl 2.0 - 2.0.0-RC5 - has been released.

please note that this release contains substantial API changes, making 
it
incompatible with all prior mod_perl 1.99 releases to date.  in other 
words,
you will need to modify ALL of your old 2.0 code before it will be able 
to
run with this latest release.  fortunately, the changes required are 
minor,
straightforward, and simple.


   *** YOU WILL NEED TO MODIFY ALL YOUR CODE AFTER UPGRADING ***


please take the time to read this document before continuing

   http://perl.apache.org/docs/2.0/rename.html

as it explains the changes, the reasons behind them, and the migration 
path
for your current codebase.

now, for the details...

The URL

     http://perl.apache.org/dist/mod_perl-2.0.0-RC5.tar.gz

has entered CPAN as

   file: $CPAN/authors/id/G/GE/GEOFF/mod_perl-2.0.0-RC5.tar.gz
   size: 1431194 bytes
    md5: a523a60b5a9758a88a0f1bdcd09eb425


Changes since RC4:

     ******************** IMPORTANT ********************
     this version of mod_perl is completely incompatible
       with prior versions of mod_perl, both 1.XX and
      1.99_XX. Please read the below changes carefully.
     ***************************************************



On Apr 20, 2005, at 10:22 PM, Foo Ji-Haw wrote:

> It looks like the latest release of MP2 RC5 has been giving new 
> installs code breaks.
>
> I don't know the full story, but I am pretty sure that the movers and 
> shakers in the decision team have a strong point for it (possibly 
> documented in perl.apache.org). It's caused me unexpected pain 
> recently as well; and I have to spend today as well working through my 
> codes because of it. But I am glad that people like Randy, Markus, and 
> the documentation team (@perl.apache.org) have jumped in to help 
> stranded people like me ('cos my job depends on my product!). Thanks 
> guys!
>
> My only wish is that there will be no more changes to the libraries in 
> such extent. After all, if this is the best way to move (mod_)perl 
> forward, we must all bite the bullet at one time or another.
>
> But for those who cannot bite it now, perhaps there can be a way to 
> download the pre-RC5 version?
>
> But no excuses for VB.NET!
>