Front page | perl.perl5.porters |
Postings from May 2009
On Wed, May 27, 2009 at 11:27:00PM -0500, Craig A. Berry wrote: > The hard part about picking cherries is knowing when they are ripe, so > I think those two paragraphs say exactly the same thing. In other > words, "cherrypick the right ones for maintperl" and "figure out if > this code is stable" are two different formulations of an identical > statement. Constructing the correct C<git cherry> commands is not the > problem. Exactly. And of course sometimes it's determining which cherries should never be picked (binary compatibility, backwards compatibility, etc etc) which may involve careful reading of the associated p5p emails, and careful examination of the patch and the files which it modifies (which might be areas of perl the pumpking is unfamiliar with). All of which takes time. > One good thing about further automation would be that new people can > be involved who don't feel they have the Perl internals knowledge to > contribute much otherwise. I vote for something that parses the > output of Test::Smoke, runs git bisect if necessary to identify the > exact commit ID when any failure first occurred, and posts a weekly > summary to p5p of what broke on what platform(s), what commit ID broke > it and what commit ID (if any) fixed it. That would get my vote too! -- Britain, Britain, Britain! Discovered by Sir Henry Britain in sixteen-oh-ten. Sold to Germany a year later for a pfennig and the promise of a kiss. Destroyed in eighteen thirty-forty two, and rebuilt a week later by a man. This we know. Hello. But what of the people of Britain? Who they? What do? And why? -- "Little Britain"Thread Previous