Revision as of 14:50, 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

Name: Jitka Plesníková
Email: <jplesnik@redhat.com>
Name: Michal Josef Špaček
Email: <mspacek@redhat.com>

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

Every Perl package will be rebuilt in a dedicated f37-perl build-root against perl 5.36.0 and then if no major problem emerges the packages will be merged back to f37 build-root.

Proposal owners:

New perl and all packages requiring perl or a Perl module will be rebuilt into f37-perl build-root.

Other developers: N/A (not a System Wide Change)

Owners of packages that fail to rebuild, mainly perl-sig users, will be asked using Bugzilla to fix or remove their packages from the distribution.

Release engineering: #Releng issue number

Release engineers will be asked for new f37-perl build-root inheriting from f37 build-root. After successful finishing the rebuild, they will be asked to merge f37-perl packages back to f37 build-root.

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

@@ Line 72: / Line 72: @@
 == Scope ==
+Every Perl package will be rebuilt in a dedicated ''f37-perl'' build-root against perl 5.36.0 and then if no major problem emerges the packages will be merged back to ''f37'' build-root.
 * Proposal owners:
-<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
+New perl and all packages requiring perl or a Perl module will be rebuilt into ''f37-perl'' build-root.
-* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
+Owners of packages that fail to rebuild, mainly perl-sig users, will be asked using Bugzilla to fix or remove their packages from the distribution.
 * Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.
+Release engineers will be asked for new ''f37-perl'' build-root inheriting from ''f37'' build-root. After successful finishing the rebuild, they will be asked to merge ''f37-perl'' packages back to ''f37'' build-root.
-The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
 * Policies and guidelines: N/A (not needed for this Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. Please submit a pull request with the proposed changes before submitting your Change proposal. -->
 * Trademark approval: N/A (not needed for this Change)
-<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://pagure.io/Fedora-Council/tickets/issues ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
 * Alignment with Objectives:
-<!-- Does your proposal align with the current Fedora Objectives: https://docs.fedoraproject.org/en-US/project/objectives/ ? It's okay if it doesn't, but it's something to consider -->
 == Upgrade/compatibility impact ==

Search

Changes/perl5.36: Difference between revisions