atom feed47 messages in org.perl.perl5-portersRe: Upgrading Perl Should be Dull and...
FromSent OnAttachments
Chia-liang KaoSep 1, 2008 8:19 am 
Moritz LenzSep 1, 2008 8:57 am 
Chia-liang KaoSep 1, 2008 9:21 am 
Nicholas ClarkSep 1, 2008 9:37 am 
Eric WilhelmSep 1, 2008 10:55 am 
Nicholas ClarkSep 1, 2008 12:05 pm 
H.Merijn BrandSep 1, 2008 1:47 pm 
chromaticSep 1, 2008 8:05 pm 
Yitzchak Scott-ThoennesSep 1, 2008 8:41 pm 
Jesse VincentSep 1, 2008 9:45 pm 
chromaticSep 1, 2008 10:50 pm 
H.Merijn BrandSep 1, 2008 11:17 pm 
Jesse VincentSep 1, 2008 11:30 pm 
Gabor SzaboSep 1, 2008 11:33 pm 
Yitzchak Scott-ThoennesSep 1, 2008 11:40 pm 
Jesse VincentSep 1, 2008 11:40 pm 
Jesse VincentSep 1, 2008 11:50 pm 
Moritz LenzSep 2, 2008 12:16 am 
Moritz LenzSep 2, 2008 12:19 am 
Sven DowideitSep 2, 2008 12:22 am 
Steffen MuellerSep 2, 2008 1:13 am 
chromaticSep 2, 2008 1:37 am 
Nicholas ClarkSep 2, 2008 1:46 am 
Andy DoughertySep 2, 2008 5:16 am 
Andy ArmstrongSep 2, 2008 5:21 am 
Chris PratherSep 2, 2008 6:57 am 
TelsSep 2, 2008 10:15 am 
chromaticSep 2, 2008 10:26 am 
chromaticSep 2, 2008 10:30 am 
David GoldenSep 2, 2008 10:30 am 
David GoldenSep 2, 2008 10:41 am 
Nicholas ClarkSep 2, 2008 10:46 am 
chromaticSep 2, 2008 10:56 am 
Nicholas ClarkSep 2, 2008 11:25 am 
David GoldenSep 2, 2008 12:29 pm 
chromaticSep 2, 2008 1:05 pm 
Dave MitchellSep 2, 2008 1:21 pm 
Nicholas ClarkSep 2, 2008 1:25 pm 
Nicholas ClarkSep 2, 2008 1:50 pm 
Eric WilhelmSep 2, 2008 4:03 pm 
Rafael Garcia-SuarezSep 3, 2008 11:21 pm 
Nicholas ClarkSep 4, 2008 12:43 am 
Aristotle PagaltzisSep 4, 2008 2:35 am 
Nicholas ClarkSep 4, 2008 2:40 am 
David CantrellSep 4, 2008 3:38 am 
David NicolSep 4, 2008 12:24 pm 
David LandgrenSep 14, 2008 1:13 pm 
Subject:Re: Upgrading Perl Should be Dull and Boring (was Re: forcing older perl to use an older version of cpan module?)
From:Jesse Vincent (jes@fsck.com)
Date:Sep 1, 2008 9:45:59 pm
List:org.perl.perl5-porters

Maybe it's possible to solve both problems by giving up the polite fiction that the feature-based release process works.

I was one of the original instigators of Parrot's monthly release plan, though I think it did postdate Nick's plan to do the same thing with Perl 5.8.

I haven't had much to do with the Parrot release cycle since its inception. It does seem to be working pretty well for Parrot and didn't work out well for Perl 5. My _guess_ about why it worked for Parrot is that we set it up with a rotating roster of monthly release engineers and a schedule 4-5 months out. If one of the volunteers couldn't do the release, the schedule just slid up a month.

Perl 5, on the other hand, has always been set up such that that the Pumpkings were both Emperor and Janitor. If the person doing the release isn't also the architect and chief coder, it might work better. And chromatic's right. When you release every month, you actually get to test your releng and upgrade tools.

chromatic,

If you were going to switch Perl over to an "every $PERIOD, whether we need it or not" release cycle, how would you do it? What can you tell p5p about what Parrot's learned about how to make the release cycle trivial and repeatable?

-Jesse