From Fedora Project Wiki
Line 68: Line 68:


== Benefit to Fedora ==
== Benefit to Fedora ==
<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
 
      Be sure to include the following areas if relevant:
      If this is a major capability update, what has changed?
          For example: This change introduces Python 5 that runs without the Global Interpreter Lock and is fully multithreaded.
      If this is a new functionality, what capabilities does it bring?
          For example: This change allows package upgrades to be performed automatically and rolled-back at will.
      Does this improve some specific package or set of packages?
          For example: This change modifies a package to use a different language stack that reduces install size by removing dependencies.
      Does this improve specific Spins or Editions?
          For example: This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server.
      Does this make the distribution more efficient?
          For example: This change replaces thousands of individual %post scriptlets in packages with one script that runs at the end.
      Is this an improvement to maintainer processes?
          For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly.
      Is this an improvement targeted as specific contributors?
          For example: Ensuring that a minimal set of tools required for contribution to Fedora are installed by default eases the onboarding of new contributors.


    When a Change has multiple benefits, it's better to list them all.
Up-to-date and latest perl release will be delivered to Fedora users.
 
    Consider these Change pages from previous editions as inspiration:
    https://fedoraproject.org/wiki/Changes/Annobin (low-level and technical, invisible to users)
    https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo (low-level, but visible to advanced users)
    https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration (primarily a UX change)
    https://fedoraproject.org/wiki/Changes/NoMoreAlpha (an improvement to distro processes)
    https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
-->


== Scope ==
== Scope ==

Revision as of 14:43, 28 April 2022

Perl 5.36

Summary

A new perl 5.36 version brings a lot of changes done over a year of development. Perl 5.36 will be released in May 20th 2022. See 5.36.0 perldelta for more details about new release. https://metacpan.org/release/SHAY/perl-5.35.11/view/pod/perldelta.pod

Owner

Current status

  • Targeted release: Fedora Linux 37
  • Last updated: 2022-04-28
  • FESCo issue: <will be assigned by the Wrangler>
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Completed Items

Items in Progress

Items to Be Done

  • Get dedicated build-root from rel-engs (f37-perl)
  • Upstream to release Perl 5.34
  • Define perl_bootstrap in perl-srpm-macros
  • Rebase perl to 5.36.0
  • Rebuild dual-lived packages (otherwise dnf recommends --skip-broken and fails)
  • Rebuild packages needed for minimal build-root
  • Rebuild packages needed for building source packages from git repository
  • Rebuild other packages: Use Fedora::Rebuild dependency solver
  • Undefine perl_bootstrap
  • Rebuild packages having perl_bootstrap condition in spec file (127 packages)
  • Rebuild all updated packages
  • Final lists of results
  • Merge dedicated build-root to rawhide and remove the dedicated one by rel-engs
  • Synchronize packages upgraded in f37 build root
  • Rebuild Perl packages: 0 of 3249 done (0.00%)

Detailed Description

New perl is released every year and updates containing mainly bug fixes follow during the year. The 5.36.0 version is stable release this year.

Feedback

Benefit to Fedora

Up-to-date and latest perl release will be delivered to Fedora users.

Scope

  • Proposal owners:
  • Other developers:
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Objectives:

Upgrade/compatibility impact

How To Test

User Experience

Dependencies

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No


Documentation

N/A (not a System Wide Change)

Release Notes