Hi Marcus -
Now that you're all done upgrading to 5.7100, it's time to help us out by
testing the next developer release of 5.8000, 5.8000_05, which was
uploaded to CPAN today.
When I perl Makefile.PL, it tells me:
This version of Catalyst conflicts with the version of
On Jan 29, 2009, at 4:34 AM, Marcus Ramberg wrote:
Now that you're all done upgrading to 5.7100, it's time to help us
out by testing the next developer release of 5.8000, 5.8000_05,
which was uploaded to CPAN today. I've included the changelog since
the previous developer release at the
Now that you're all done upgrading to 5.7100, it's time to help us out by
testing the next developer release of 5.8000, 5.8000_05, which was uploaded
to CPAN today. I've included the changelog since the previous developer
release at the bottom of the mail.
In case you want to help out with the
Sorry to jump in so late here, but has there been any discussion on
moving decoding requests into core? Requests come in octets and end
up in Perl as parameters which are used as (typically) character
strings. So, really should decode every request based on the request
charset if provided, no?
Am Donnerstag, den 29.01.2009, 10:34 +0100 schrieb Marcus Ramberg:
Now that you're all done upgrading to 5.7100, it's time to help us out
by testing the next developer release of 5.8000, 5.8000_05, which was
uploaded to CPAN today.
Thanks, great job!
t/optional_memleak.t fails some of its
On 29 Jan 2009, at 19:51, Frank Wiegand wrote:
t/optional_memleak.t fails some of its tests.
Is this something to worry about?
See also RT Ticket #42540, which was filled against 5.7100.
No, its not.. This is a known issue with the test which hasn't been
solved yet.
5.8000_04 _did_ leak
