From Fedora Project Wiki
 
(64 intermediate revisions by 4 users not shown)
Line 2: Line 2:


== Summary ==
== 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 [https://metacpan.org/pod/release/SHAY/perl-5.35.11/pod/perldelta.pod 5.36.0 perldelta] for more details about new release.
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 28th 2022. See [https://metacpan.org/release/RJBS/perl-5.36.0/view/pod/perldelta.pod perldelta] for more details about new release.
https://metacpan.org/release/SHAY/perl-5.35.11/view/pod/perldelta.pod


== Owner ==
== Owner ==
* Name: [[User:Jplesnik| Jitka Plesníková]]
* Name: [[User:Jplesnik| Jitka Plesníková]], [[User:Mspacek| Michal Josef Špaček]]
* Email: <jplesnik@redhat.com>
* Email: <jplesnik@redhat.com>, <mspacek@redhat.com>
* Name: [[User:Mspacek| Michal Josef Špaček]]
* Email: <mspacek@redhat.com>
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
Line 15: Line 12:


== Current status ==
== Current status ==
[[Category:ChangePageIncomplete]]
[[Category:ChangeAcceptedF37]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
Line 25: Line 22:
[[Category:SystemWideChange]]
[[Category:SystemWideChange]]


* Targeted release: [[Releases/37 | Fedora Linux 37 ]]  
* Targeted release: [[Releases/37/ChangeSet| Fedora Linux 37 ]]  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
Line 33: Line 30:
ON_QA -> change is fully code complete
ON_QA -> change is fully code complete
-->
-->
* FESCo issue: <will be assigned by the Wrangler>
* [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/ZYPUXNRJNZ3UNQCN6IHBLRKT2TY3HWTT/ devel list]
* Tracker bug: <will be assigned by the Wrangler>
* FESCo issue: [https://pagure.io/fesco/issue/2791 #2791]
* Release notes tracker: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2088002 #2088002]
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/840 #840]


=== Completed Items ===
=== Completed Items ===
 
* Get dedicated [https://pagure.io/releng/issue/10771#comment-795497 build-root from rel-engs (''f37-perl'')]
=== Items in Progress ===
* Upstream to release Perl 5.36
 
=== Items to Be Done ===
 
* Get dedicated <!--[https://pagure.io/releng/issue/10119 --> build-root from rel-engs (''f37-perl'') <!-- ] -->
* Upstream to release Perl 5.34
<!--* Remove old perl(:MODULE_COMPAT_5.34.*) from perl -->
* Define perl_bootstrap in perl-srpm-macros
* Define perl_bootstrap in perl-srpm-macros
* Rebase perl to 5.36.0
* Rebase perl to 5.36.0
<!--* Build new perl 5.36 keeping old COMPAT Provides -->
* Rebuild dual-lived packages (otherwise dnf recommends --skip-broken and fails)
* Rebuild dual-lived packages (otherwise dnf recommends --skip-broken and fails)
* Rebuild packages needed for minimal build-root
* Rebuild packages needed for minimal build-root
Line 54: Line 45:
* Rebuild other packages: Use Fedora::Rebuild dependency solver
* Rebuild other packages: Use Fedora::Rebuild dependency solver
* Undefine perl_bootstrap
* Undefine perl_bootstrap
* Rebuild packages having perl_bootstrap condition in spec file (127 packages)
* Rebuild packages having perl_bootstrap condition in spec file (129 packages)
* Rebuild all updated packages
* Rebuild all updated packages
* [https://jplesnik.fedorapeople.org/5.36/ Final lists of results]
* [https://jplesnik.fedorapeople.org/5.36/ Final lists of results]
* Merge dedicated build-root to rawhide and remove the dedicated one by rel-engs
* Merge dedicated build-root to rawhide and remove the dedicated one by rel-engs
* Synchronize packages upgraded in ''f37'' build root
* Synchronize packages upgraded in ''f37'' build root
* Rebuild Perl packages: 0 of 3249 done (0.00%)
 
=== Items in Progress ===
* Rebuild Perl packages: 3265 of 3266 done (99.97 %)
* Failed packages (1):
** gplugin - [https://bugzilla.redhat.com/show_bug.cgi?id=2093218 BZ#2093218] - only ppc64le
* Rebuild Fedora modules: 2 of 7 (28.57 %)
** nginx:mainline - DONE
** nginx:1.20
** postgresql:10
** postgresql:11
** postgresql:12
** postgresql:14
** subversion:1.14 - DONE
 
=== Items to Be Done ===


== Detailed Description ==
== 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.
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 ==
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. -->


== 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:
== Scope ==
    https://fedoraproject.org/wiki/Changes/Annobin (low-level and technical, invisible to users)
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.
    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 ==
* Proposal owners:
* 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 -->
* Release engineering: [https://pagure.io/releng/issue/10771 #10771] <!-- 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 -->
* Policies and guidelines: N/A (not needed for this Change)  
<!-- 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)
* 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:  
* 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 ==
== Upgrade/compatibility impact ==
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
Vast majority of functionality will be preserved. Only the packages that failed to build against perl 5.36 will be removed from the distribution. That will require to remove those packages from the existing systems otherwise a package manager will encounter unsatisfied dependencies. The developers in Perl language are advised to install ''perl-doc'' and ''perl-debugger'' packages.
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->


== How To Test ==
== How To Test ==
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.  
Try upgrading from Fedora 36 to 37. Try some Perl application to verify they work as expected. Try embedded perl in [https://src.fedoraproject.org/rpms/openldap slapd] or [https://src.fedoraproject.org/rpms/net-snmp snmpd].
 
Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
 
A good "how to test" should answer these four questions:
 
0. What special hardware / data / etc. is needed (if any)?
1. How do I prepare my system to test this change? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the change is
working like it's supposed to?
3. What are the expected results of those actions?
-->
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->


== User Experience ==
== User Experience ==
<!-- If this change proposal is noticeable by users, how will their experiences change as a result?
There should not be any remarkable change in user experience. With the exception that previously locally installed modules with a CPAN clients will need a reinstallation.
 
This section partially overlaps with the Benefit to Fedora section above. This section should be primarily about the User Experience, written in a way that does not assume deep technical knowledge. More detailed technical description should be left for the Benefit to Fedora section.
 
Describe what Users will see or notice, for example:
  - Packages are compressed more efficiently, making downloads and upgrades faster by 10%.
  - Kerberos tickets can be renewed automatically. Users will now have to authenticate less and become more productive. Credential management improvements mean a user can start their work day with a single sign on and not have to pause for reauthentication during their entire day.
- Libreoffice is one of the most commonly installed applications on Fedora and it is now available by default to help users "hit the ground running".
- Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
-->


== Dependencies ==
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
There is more than 3200 packages depending on perl. Most of them are expected not to break. Finishing this change can be endangered only by critical changes in a toolchain.
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->


== Contingency Plan ==
== Contingency Plan ==


<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency mechanism: If we find perl 5.36 is not suitable for Fedora 37, we will revert back to perl 5.34 and we drop the temporary build-root with already rebuilt packages.
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency deadline: branching Fedora 37 from Rawhide.
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks release? No.
 


== Documentation ==
== Documentation ==
<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
* [https://metacpan.org/release/RJBS/perl-5.36.0/view/pod/perldelta.pod 5.36.0 perldelta]
 
* [https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/thread/4JFWDKMYKEMLTUQSIUIHZZNGM5UP76EM/ An announcement on perl-devel mailing list]
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/ZYPUXNRJNZ3UNQCN6IHBLRKT2TY3HWTT/ An announcement on fedora-devel mailing list]
N/A (not a System Wide Change)


== Release Notes ==
== Release Notes ==
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
* Core Enhancements
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this change, indicate them here. A link to upstream documentation will often satisfy this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release.
** a new commmand-line flag ''-g'' which it is alias for -0777
 
** Unicode 14.0 is supported
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
** regex sets are no longer considered experimental
-->
** Variable length lookbehind is mostly no longer considered experimental
** ''SIGFPE'' no longer deferred
** iterating over multiple values at a time (experimental)
** new module ''builtin'' which provides documentation for new always-present functions that are built into the interpreter (experimental)
** adds support for ''defer'' blocks, which are blocks of code prefixed by the ''defer'' modifier (experimental)
** ''try''/''catch'' syntax has been extended to support an optional third block introduced by the ''finally'' keyword (experimental)
** non-ASCII delimiters for quote-like operators (experimental)
** @_ is now experimental within signatured subs
* Incompatible Changes
** A physically empty ''sort'' is now a compile-time error
* Deprecations
** ''use VERSION'' (where VERSION is below v5.11) after ''use v5.11'' is deprecated
* Lots of modules were updated
* Changes in errors and warnings can cause failures in tests
* Performance Enhancements
** Perl now probe for compiler support for C11 thread local storage, and where available use this for "implicit context" for XS extensions making API calls for a threaded Perl build. This requires fewer function calls at the C level than POSIX thread specific storage.

Latest revision as of 12:17, 13 December 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 28th 2022. See perldelta for more details about new release.

Owner

Current status

Completed Items

  • Get dedicated build-root from rel-engs (f37-perl)
  • Upstream to release Perl 5.36
  • 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 (129 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

Items in Progress

  • Rebuild Perl packages: 3265 of 3266 done (99.97 %)
  • Failed packages (1):
  • Rebuild Fedora modules: 2 of 7 (28.57 %)
    • nginx:mainline - DONE
    • nginx:1.20
    • postgresql:10
    • postgresql:11
    • postgresql:12
    • postgresql:14
    • subversion:1.14 - DONE

Items to Be Done

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.

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 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

Vast majority of functionality will be preserved. Only the packages that failed to build against perl 5.36 will be removed from the distribution. That will require to remove those packages from the existing systems otherwise a package manager will encounter unsatisfied dependencies. The developers in Perl language are advised to install perl-doc and perl-debugger packages.

How To Test

Try upgrading from Fedora 36 to 37. Try some Perl application to verify they work as expected. Try embedded perl in slapd or snmpd.

User Experience

There should not be any remarkable change in user experience. With the exception that previously locally installed modules with a CPAN clients will need a reinstallation.

Dependencies

There is more than 3200 packages depending on perl. Most of them are expected not to break. Finishing this change can be endangered only by critical changes in a toolchain.

Contingency Plan

  • Contingency mechanism: If we find perl 5.36 is not suitable for Fedora 37, we will revert back to perl 5.34 and we drop the temporary build-root with already rebuilt packages.
  • Contingency deadline: branching Fedora 37 from Rawhide.
  • Blocks release? No.

Documentation

Release Notes

  • Core Enhancements
    • a new commmand-line flag -g which it is alias for -0777
    • Unicode 14.0 is supported
    • regex sets are no longer considered experimental
    • Variable length lookbehind is mostly no longer considered experimental
    • SIGFPE no longer deferred
    • iterating over multiple values at a time (experimental)
    • new module builtin which provides documentation for new always-present functions that are built into the interpreter (experimental)
    • adds support for defer blocks, which are blocks of code prefixed by the defer modifier (experimental)
    • try/catch syntax has been extended to support an optional third block introduced by the finally keyword (experimental)
    • non-ASCII delimiters for quote-like operators (experimental)
    • @_ is now experimental within signatured subs
  • Incompatible Changes
    • A physically empty sort is now a compile-time error
  • Deprecations
    • use VERSION (where VERSION is below v5.11) after use v5.11 is deprecated
  • Lots of modules were updated
  • Changes in errors and warnings can cause failures in tests
  • Performance Enhancements
    • Perl now probe for compiler support for C11 thread local storage, and where available use this for "implicit context" for XS extensions making API calls for a threaded Perl build. This requires fewer function calls at the C level than POSIX thread specific storage.
Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/perl5.36&oldid=663097"