https://fedoraproject.org/wiki/Changes/php81
== Summary ==
Update the PHP stack in Fedora to latest version 8.1.x
== Owner ==
* Name: [[User:Remi| Remi Collet]] and [[SIGs/PHP|PHP SIG]]
* Email: remi at fedoraproject dot org
== Current status ==
* An testing module is available in my
[https://blog.remirepo.net/post/2021/09/02/PHP-on-the-road-to-the-8.1.0-rele…]
* List of [https://github.com/remicollet/remirepo/issues/177
extensions compatibility list]
* [https://wiki.php.net/todo/php81 Upstream schedule for 8.1]
* Sep 30th 2020 PHP 8.1.0RC1 was released
== Detailed Description ==
Update the PHP stack in Fedora to latest version 8.1.x.
Fedora have a 6 months cycle, PHP and a 1 year, 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)
== Benefit to Fedora ==
Provides the latest PHP version to developers and system administrators.
== 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: N/A
* Policies and guidelines: N/A
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
N/A (not a System Wide Change)
== How To Test ==
* The PHP stack (extensions and libraries) are monitored by Koschei,
see the [https://apps.fedoraproject.org/koschei/groups/php?order_by=state%2C-started
Koschei PHP group]
* install and play with your web applications
== User Experience ==
Developers and system administrators will have the great benefit or
running the latest PHP version.
== Dependencies ==
All php-* packages (and some *-php)
== Contingency Plan ==
* Contingency mechanism: Drop not compatible packages.
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change)
== Documentation ==
* [https://www.php.net/manual/en/migration80.php Migrating from PHP
8.0.x to PHP 8.1.x]
* [https://raw.githubusercontent.com/php/php-src/PHP-8.1/UPGRADING UPGRADING]
* [https://raw.githubusercontent.com/php/php-src/PHP-8.1/UPGRADING.INTERNALS
UPGRADING.INTERNALS]
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
Fedora Linux 35 Beta Released
------------------------------------------
The Fedora Project is pleased to announce the immediate availability
of Fedora 35 Beta, the next step towards our planned Fedora 35 release
at the end of October.
Download the prerelease from our Get Fedora site:
* Get Fedora 35 Beta Workstation: https://getfedora.org/workstation/download/
* Get Fedora 35 Beta Server: https://getfedora.org/server/download/
* Get Fedora 35 IoT: https://getfedora.org/iot/download/
Or, check out one of our popular variants, including KDE Plasma, Xfce,
and other desktop environments, as well as images for ARM devices:
* Get Fedora 35 Beta Spins: https://spins.fedoraproject.org/prerelease
* Get Fedora 35 Beta Labs: https://labs.fedoraproject.org/prerelease
* Get Fedora 35 Beta ARM: https://arm.fedoraproject.org/prerelease
## Beta Release Highlights
* Fedora 35 Workstation Beta includes GNOME 41
* Fedora Kinoite—a KDE Plasma environment based on rpm-ostree technology
* Fedora Linux 35 builds on the switch to PipeWire for managing audio
by introducing WirePlumber as the default session manager.
* Python 3.10, Perl 5.34, PHP 8.0 updated versions.
* And more ...
For more details about the release, read the full announcement at
* https://fedoramagazine.org/announcing-fedora-35-beta/
or look for the prerelease pages in the download sections at
* https://getfedora.org/
Since this is a Beta release, we expect that you may encounter bugs or
missing features. To report issues encountered during testing, contact
the Fedora QA team via the test(a)lists.fedoraproject.org mailing list or
in #fedora-qa on Libera Chat.
Regards,
Mohan Boddu
Fedora Release Engineering.
I'm passing along a lightly-edited announcement from the Red Hat
Bugzilla admins. You may have noticed this change already. The short
version is that the search API now defaults to returning 20 bugs, but
authenticated calls can request up to 1000.
More details are on the Community Blog:
https://communityblog.fedoraproject.org/changes-to-bugzilla-queries/
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
https://fedoraproject.org/wiki/Changes/ExcludeFromWeakAutodetect
== Summary ==
exclude_from_weak_autodetect enables autodetection of unmet weak
dependencies (Recommends or Supplements) of installed packages and
blocks installation of packages satisfying already unmet dependencies.
In other words: When you don't have the recommended package installed,
it won't be automatically installed with future upgrades of the
recommending package.
== Owner ==
* Name: [[User:jmracek| Jaroslav Mracek]]
* Email: jmracek(a)redhat.com
== Detailed Description ==
The feature is designed to prevent an install of removed weak
dependencies from the system by users and to not install weak
dependencies missing after system deployment. It will change the
behavior of DNF, microdnf, and PackageKit. The feature will be
backported to all Fedoras, but in default, the feature will be off.
Additional information: https://bugzilla.redhat.com/show_bug.cgi?id=1699672
The default value for exclude_from_weak_autodetect configuration can
be overridden in `/etc/dnf/dnf.conf`
== Feedback ==
The feature was requested by [[User:Churchyard|Miro Hrončok]] and
supported by many others: See
[https://bugzilla.redhat.com/show_bug.cgi?id=1699672 rhbz#1699672] for
more feedback.
== Benefit to Fedora ==
After the installation of a fresh system, the first upgrade will not
install a lot of weak dependencies. Some of them were excluded from
the kick-start installation set for good reasons (security, image
size, minimal functional set, ...), but after the first update, all
weak dependencies are installed, therefore some features of deployment
simply disappear.
== Scope ==
* Proposal owners:
** The feature is ready in Pull Request -
https://github.com/rpm-software-management/libdnf/pull/1279
** PRs only wait for a release of libsolv
** The Feature will be enabled in upstream as default, therefore from
Fedora 36, we start to release libdnf without a revert patch of
default in comparison to upstream.
* Other developers: The change requires a new release of libsolv.
* Release engineering:
* Policies and guidelines: A packaging guideline should be added that
discourages or forbids weak dependencies on fully versioned
(sub)packages (see
[https://bugzilla.redhat.com/show_bug.cgi?id=1699672#c44 the
details]).
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives:
== Upgrade/compatibility impact ==
No manual changes will be required. After the libdnf update, this
feature will be on by default.
== How To Test ==
1. Install package without satisfied weak dependencies
2. Upgrade the upgrade. With exclude_from_weak_autodetect=true, it
will not install weak dependencies of already installed packages. With
exclude_from_weak_autodetect=false, weak dependencies will be
installed during upgrades.
== User Experience ==
The change in default will help to keep some values for particular
deployments (a minimal system will be still minimal without disabling
weak dependencies).
Users will be able to remove particular weak dependencies and they
will be not installed on the first upgrade.
In case when the feature will not work according to the user
expectation it can be switched off in the dnf configuration file.
== Dependencies ==
libsolv - Required code changes are already in the libsolv upstream.
We only wait for the next libsolv release.
== Contingency Plan ==
There are no external dependencies, therefore we can easily postpone
the feature and the change of default behavior.
* Contingency mechanism: (What to do? Who will do it?)
* Contingency deadline: beta freeze
* Blocks release? No
== Documentation ==
The feature will be documented in dnf man pages.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
Due to outstanding blocker bugs, we do not have an F35 Beta RC. As a
result, F35 Beta is NO-GO by default and tomorrow's Go/No-Go meeting
is cancelled.
The next Fedora Linux 35 Beta Go/No-Go meeting[1] will be held at 1700
UTC on Thursday 23 September in #fedora-meeting. We will aim for the
"target date #2" milestone of 28 September. The release schedule[2]
has been updated accordingly. This change does not impact the final
release date.
[1] https://calendar.fedoraproject.org/Fedora%20release/2021/9/23/#m10064
[2] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
Due to outstanding blocker bugs, we do not have an F35 Beta RC. As a
result, F35 Beta is NO-GO by default and tomorrow's Go/No-Go meeting
is cancelled.
The next Fedora Linux 35 Beta Go/No-Go meeting[1] will be held at 1700
UTC on Thursday 16 September in #fedora-meeting. We will aim for the
"target date #1" milestone of 21 September. The release schedule[2]
has been updated accordingly. This change does not impact the final
release date.
[1] https://calendar.fedoraproject.org/Fedora%20release/2021/9/16/#m10064
[2] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis