FAQ
As of now, I'm planning to build and CPAN Perl 5.12.0 this Friday night
with an announcement on Saturday morning.

Before then, I plan to update perldelta to describe a known issue with
CPANPLUS's tests which wasn't fixed for RC4. I do not plan to apply the
proposed patch for this issue before 5.12.0, but will for .1.

When I tag v5.12.0, I'll also create the maint-5.12 branch and bump the
version in blead to 5.13.0. At that point, I'd really like committers
to not go too wild on blead until we get 5.12.1 nailed down.

According to Porting/release_schedule.pod, Leon Brocard will ship v5.13.0
on April 20th.

Assuming that I tag v5.12.0 on April 9, we'll push v5.12.1-RC1 on April
30 or May 1 with the final release a week later.

-Jesse

--

Search Discussions

  • Reini Urban at Apr 8, 2010 at 5:39 pm

    Jesse Vincent schrieb:
    As of now, I'm planning to build and CPAN Perl 5.12.0 this Friday night
    with an announcement on Saturday morning.

    Before then, I plan to update perldelta to describe a known issue with
    CPANPLUS's tests which wasn't fixed for RC4. I do not plan to apply the
    proposed patch for this issue before 5.12.0, but will for .1.
    When you plan to describe known issues, you can also mention that
    several cygwin patches did not went it (again), and the poor user should
    try the official cygwin release instead before complaining
    at p5p.

    run-time issues:
    * "Bug#55162 File::Spec::case_tolerant performance"
    * "CYG11 no-bs"
    * "CYG12 otherlibdirs"
    * "CYG14 DynaLoader cyg*.dll"
    * "CYG15 static Win32CORE"
    * "CYG17 cyg-1.7 paths-utf8"
    * "CYG20 Config{libperl} dll"
    * "CYG24 Build man pages too"
    * "CYG25 rebase privlib"

    I started tracking them for blead now here:
    http://github.com/rurban/perl/commits/cygwin

    The release patches are here:
    http://code.google.com/p/cygwin-rurban/source/browse/trunk/release/perl
    --
    Reini Urban
  • Jesse Vincent at Apr 8, 2010 at 5:41 pm

    On Thu, Apr 08, 2010 at 07:39:25PM +0200, Reini Urban wrote:
    Jesse Vincent schrieb:
    As of now, I'm planning to build and CPAN Perl 5.12.0 this Friday night
    with an announcement on Saturday morning.

    Before then, I plan to update perldelta to describe a known issue with
    CPANPLUS's tests which wasn't fixed for RC4. I do not plan to apply the
    proposed patch for this issue before 5.12.0, but will for .1.
    When you plan to describe known issues, you can also mention that
    several cygwin patches did not went it (again), and the poor user
    should try the official cygwin release instead before complaining
    at p5p.
    Ok. Are there rt.perl.org ticket numbers for these yet?


    run-time issues:
    * "Bug#55162 File::Spec::case_tolerant performance"
    * "CYG11 no-bs"
    * "CYG12 otherlibdirs"
    * "CYG14 DynaLoader cyg*.dll"
    * "CYG15 static Win32CORE"
    * "CYG17 cyg-1.7 paths-utf8"
    * "CYG20 Config{libperl} dll"
    * "CYG24 Build man pages too"
    * "CYG25 rebase privlib"

    I started tracking them for blead now here:
    http://github.com/rurban/perl/commits/cygwin

    The release patches are here:
    http://code.google.com/p/cygwin-rurban/source/browse/trunk/release/perl
    --
    Reini Urban
    --
  • Nicholas Clark at Apr 9, 2010 at 9:23 am

    On Thu, Apr 08, 2010 at 01:26:15PM -0400, Jesse Vincent wrote:
    As of now, I'm planning to build and CPAN Perl 5.12.0 this Friday night
    with an announcement on Saturday morning.

    Before then, I plan to update perldelta to describe a known issue with
    CPANPLUS's tests which wasn't fixed for RC4. I do not plan to apply the
    proposed patch for this issue before 5.12.0, but will for .1.

    When I tag v5.12.0, I'll also create the maint-5.12 branch and bump the
    version in blead to 5.13.0. At that point, I'd really like committers
    to not go too wild on blead until we get 5.12.1 nailed down.
    Is the first thing to be done post-branch on blead bumping the version to
    5.13.0?
    According to Porting/release_schedule.pod, Leon Brocard will ship v5.13.0
    on April 20th.
    Also, I was wondering, whether a few more days would hurt much, and that
    we don't actually re-open blead completely* until 5.13.0 ships, such that
    there's a clear public "start" point for basing branches off.

    Nicholas Clark

    * "completely" is also a variety of options. For example, we could move back
    to "feature freeze", and so only commit fixes to bugs pre 5.13.0

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupperl5-porters @
categoriesperl
postedApr 8, '10 at 5:26p
activeApr 9, '10 at 9:23a
posts4
users3
websiteperl.org

People

Translate

site design / logo © 2022 Grokbase