Craig A. Berry wrote: > On Sat, Feb 21, 2009 at 4:06 AM, Michael G Schwern <schw...@pobox.com> wrote: >> Nicholas Clark wrote: >>> Applied to blead as 1487aac67a72b9f87b24113f65b4d878401bee33 >> Thanks. > > There's a new failure on VMS, but this should take care of it: > > http://rt.cpan.org/Public/Bug/Display.html?id=43511
I'll get that in and your other VMS patches. Thanks. >>> should I be raising RT tickets for these instead? >> Keep raising RT tickets. > > Does that mean CPAN is upstream, as in: The CPAN MakeMaker has always been upstream, though by the definition in Maintainers.pl it should probably be set to "first-come" which is what has been done in practice. > Or is MakeMaker too essential to building the core for upstream to > really mean anything? And is GitHub the best place to host MakeMaker, > or could it be put on git.perl.org and pumpkings given write access > for emergencies, like when there is a release coming up but Michael is > away from e-mail for awhile. I'm just thinking out loud -- if that > involves too much work by too many people, then just pulling from > GitHub does look like an improvement over applying patches. The pumpkings have never needed write access to the MakeMaker repository to make changes to their copy in Perl, or even to make an emergency CPAN release. Moving to github doesn't change that. What it does change it making it a whole lot easier to keep in sync with blead, for others to work on MakeMaker and for me to integrate that work. The MakeMaker fork on github is basically working. There's some nits to be ironed out, and I want to change the way the modules in ext/ are tested, but it looks like it's going to work. -- There will be snacks.
