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

blead-bugfix branch? (was Re: Perl 5.10.1)

Thread Next
David Golden
June 30, 2009 08:42
blead-bugfix branch? (was Re: Perl 5.10.1)
Message ID:
On Tue, Jun 30, 2009 at 11:18 AM, Nicholas Clark<> wrote:
> Which is why I'm trying to get everything possible moved from lib/ to ext/
> so that it's obvious what's core and what needs to be treated as dual.

I think perlhack says that lib is for pure perl and ext is for XS.  If
that's changing, what should it be?  Are all dual-life modules
supposed to move to ext?

> I don't object to the end results you wish to achieve, because actually
> they're the end results that I'd like to see to. But I think that the
> way to get there is identifying and implementing incremental changes needed
> to get from where we are now to where we want to be. Which, to my mind,
> means people prepared to get their hands dirty helping, and working with
> the people already doing things, rather than writing lots of e-mail
> without contributing time or code.

One specific incremental step I recommend, then, is to create a
blead-bugfix branch.  Have bug-closing changes committed there, and
merge it into blead regularly.  Let all new feature/optimization
development continue on blead.  blead-bugfix should change more slowly
and be more stable and at the very least will allow testing bug fixes
in isolation from new innovation.  I would think it would be a primary
place for cherry picking commits back to maint.

In that two-part schema, dual-life module updates should probably go
on blead, since they could be introducing new bugs.  But if a very
limited change were made to close a perl RT bug, it could arguably go
on blead-bugfix.  I would leave that to committers discretion.

Pumpkings past and current should weigh in whether this would help.  I
know if I were pumpking, it's how I'd want things broken out.
(Particularly since git makes all the repeated merging so painless.)

> [And, as usual, if anyone thinks that this is a personal attack, think
> again. David Golden is working bloody hard on Module::Build, and I'm sure
> that if anyone would like to help get things done, but the core doesn't
> appeal, I know that he'd welcome help there:
> ]

[/me smiles] Thanks for the plug.  Triage is mostly done on M::B --
now we're blocking on patches.  But I've since adopted EU::CBuilder
and EU::ParseXS as well, and I haven't had a chance to triage those
lists and could use help there, though I suspect that no additional
bug fixes will happen until after 5.10.1 (assuming a release candidate
in the next couple weeks).

-- David

Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About