FAQ
Ken -- I tried to be "helpful" sending p5p a patch to merge 0.31 into blead
for the 5.10.1.

Unfortunately, as per my other email, they went off and patched M::B in
blead without pushing it upstream.

I just committed the change, bumped versions to 0.3101 and added a Changes
note. All that needs to be done for a 0.3101 release is to timestamp the
Changes entry and kick the dist out the door to CPAN.

I'll resubmit the blead patch based on this new version.

-- David

Search Discussions

  • Adam Kennedy at Jan 7, 2009 at 11:51 pm
    Methinks a nightly cron job to detect differences between core and
    current CPAN stable and mail a snarky message to p5p? :)

    Adam K

    2009/1/8 David Golden <xdaveg@gmail.com>:
    Ken -- I tried to be "helpful" sending p5p a patch to merge 0.31 into blead
    for the 5.10.1.

    Unfortunately, as per my other email, they went off and patched M::B in
    blead without pushing it upstream.

    I just committed the change, bumped versions to 0.3101 and added a Changes
    note. All that needs to be done for a 0.3101 release is to timestamp the
    Changes entry and kick the dist out the door to CPAN.

    I'll resubmit the blead patch based on this new version.

    -- David
  • Nicholas Clark at Jan 8, 2009 at 10:55 am

    On Thu, Jan 08, 2009 at 10:51:50AM +1100, Adam Kennedy wrote:
    Methinks a nightly cron job to detect differences between core and
    current CPAN stable and mail a snarky message to p5p? :)
    Blame attribution on the lines that are different would allow it to announce
    whodunnit.

    Nicholas Clark

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmodule-build @
categoriesperl
postedJan 7, '09 at 3:20p
activeJan 8, '09 at 10:55a
posts3
users3
websitecpan.org...

People

Translate

site design / logo © 2018 Grokbase