Re: Perl 5.10.1

Front page | perl.perl5.porters | Postings from June 2009

Thread Previous | Thread Next

From:

Nicholas Clark

Date:

June 30, 2009 13:42

Subject:

Re: Perl 5.10.1

Message ID:

20090630204219.GO33745@plum.flirble.org

On Tue, Jun 30, 2009 at 01:00:05PM -0700, David E. Wheeler wrote:
> On Jun 30, 2009, at 12:44 PM, Nicholas Clark wrote:

> >1: Merge schwern's existing branch that changes tests in ext to run  
> >with
> >  the current directory set to ext/Foo-Bar rather than t/
> 
> Link/discussion?

http://groups.google.com/group/perl.perl5.porters/browse_thread/thread/f1a3036d2a795642/425f889951e674c6

> >2: Migrate dual life modules from lib to ext, in the process
> >  a: Rearranging the files structure in blead to be identical to  
> >their CPAN
> >     tarball
> >  b: Making the tests pass from ext/whatever (because right now  
> >they're all
> >     running with the chdir as t/)
> >3: See what's left in lib
> 
> Oh, this is do-able by pretty much anyone who puts code on CPAN.  
> Perhaps a bunch of us could do this at a hackathon at OSCON? I'm  
> assuming 1.10.1 will be out by then.

Eyeballing perlhist.pod, the rough time between *RC1 and release for 5.8.2
to 5.8.8 was 7 to 11 days.

5.10.0-RC1 to 5.10.1 was 31.
5.8.9-RC1 to 5.8.9 34.

I don't remember the details for 5.10.0, but 5.8.9 hit some showstopper
regressions (some involving CVEs, and not re-introducing them)

So if 5.10.1 hits the something similar, I doubt it will
"escape to manufacturing" in the 21 days between now and then.

Dave isn't doing a talk about 5.10.1 anywhere, so there's no motivation of
"conference driven development" [I can't remember who coined that term]

> Why not introduce such deprecations in 1.10.2 and make them go away in  
> 5.12? Too much work?

Well, I don't think that it's written down anywhere outside the list
archives, but the policy is no new warnings (of which deprecations are one
class) within a stable branch.

> >a: CPAN and CPANPLUS knowing which core modules are deprecated.
> >  (The list is currently just Switch, but will get longer before 5.12)
> 
> Could such a list go into an installed file that CPAN(?:PLUS)? could  
> just read?

No need, if it's possible to avoid needing a list at all:

> >"a" and "b" might be possible simply by having deprecate.pm record  
> >all modules
> >that called it that would trigger the warning, and have CPAN/CPANPLUS
> >interrogate that.

> Do we have cpan testers who regularly build from blead and test CPAN  
> modules with it? That way they can notify said authors of any issues.  
> That would be a way to get more CPAN authors involved more quickly. I  
> seem to recall that someone did this for 1.10RC1, but it'd be nice to  
> do it in blead all the time. Continuous testing, that is.

I don't know.

I think someone (Slaven?) said that there was a push to test some time
before 5.10, authors were notified of problems, and many didn't fix things.

If I remember, I can ask any that I bump into at YAPC::EU

Nicholas Clark

Thread Previous | Thread Next