F42 Change Proposal: PHP 8.2 (Self-Contained)

Project Discussion Change Proposals
, ,
1

PHP 8.4

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Wiki
Announced

:link: Summary

Update the PHP stack in Fedora to the latest version 8.4.x

:link: Owner

:link: Current status

Version 8.4.0 GA is planed for November 21th.

:link: Detailed Description

Update the PHP stack in Fedora to latest version 8.4.x.

Fedora has a 6 months cycle, PHP a 1 year cycle, our common practice for some years:

  • 2 Fedora cycles for each PHP minor release (exceptions below)
  • 3 Fedora cycles for latest minor (e.g. 5.6 or 7.4) to give more time before next major
  • 1 Fedora cycle for first major (e.g. 7.0 or 8.0)

Fedora 38 and 39 have PHP 8.2, Fedora 40 and 41 have PHP 8.3.

As this version should be the last 8.x (before 9.0), it should be in Fedora 42, 43 and 44.

:link: Benefit to Fedora

Provides the latest PHP version to developers and system administrators.

:link: Scope

  • Proposal owners: Check Koschei status. Test with latest version to ensure compatibility. Work with upstream on bug fixing. Needed mass rebuild (C extensions) done by change owner.

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

  • Release engineering:#Releng issue number

  • List of deliverables: N/A (not a System Wide Change)

  • Policies and guidelines: N/A (not a System Wide Change)

  • Trademark approval: N/A (not needed for this Change)

:link: Upgrade/compatibility impact

N/A (not a System Wide Change)

:link: How To Test

  • The PHP stack (extensions and libraries) are monitored by Koschei, see the Koschei PHP group
  • install and play with your web applications

:link: User Experience

Developers and system administrators will have the great benefit or running the latest PHP version.

:link: Dependencies

All php-* packages (and some *-php)

:link: Contingency Plan

  • Contingency mechanism: Drop not compatible (and not fixable) packages.

  • Contingency deadline: N/A (not a System Wide Change)

  • Blocks release? N/A (not a System Wide Change), Yes/No

  • Blocks product? product

:link: Documentation

:link: Release Notes

Last edited by @amoloney 2024-09-12T16:22:59Z

Last edited by @amoloney 2024-09-12T16:22:59Z

2

How do you feel about the proposal as written?

  • Strongly in favor
  • In favor, with reservations
  • Neutral
  • Opposed, but could be convinced
  • Strongly opposed
0 voters

If you are in favor but have reservations, or are opposed but something could change your mind, please explain in a reply.

We want everyone to be heard, but many posts repeating the same thing actually makes that harder. If you have something new to say, please say it. If, instead, you find someone has already covered what you’d like to express, please simply give that post a :heart: instead of reiterating. You can even do this by email, by replying with the heart emoji or just “+1”. This will make long topics easier to follow.

Please note that this is an advisory “straw poll” meant to gauge sentiment. It isn’t a vote or a scientific survey. See About the Change Proposals category for more about the Change Process and moderation policy.

3

The subject is likely wrong and should be “8.4”

1 Like
4

Note that as far as I know, it is not guaranteed that there won’t be a PHP 8.5 - (see this message as the most recent discussion on 8.5 vs 9, from what I can tell).

For PHP 7.4, it was clear multiple months before 7.4 Alpha release that the next version would be 8.0, see this message. This is not the case this time, as 8.4 is already in the Beta stage.
(Indeed, when PHP 8 was proposed after 7.3, there was pushback to ensure there would be time for deprecations.)
To me, this indicates that an 8.5 release may be more likely this time.

5

This change proposal has now been submitted to FESCo with ticket #3275 for voting.

To find out more, please visit our Changes Policy documentation.