https://fedoraproject.org/wiki/Changes/perl5.30
== Summary ==
A new ''perl 5.30'' version brings a lot of changes done over a year
of development. Perl 5.30 should be released at the end of May 2019.
See [https://metacpan.org/pod/release/XSAWYERX/perl-5.30.0-RC1/pod/perldelta.pod
5.30.0 perldelta] for more details about preparing release.
== Owner ==
* Name: [[User:Jplesnik| Jitka Plesníková]]
* Email: <jplesnik(a)redhat.com>
* Name: [[User:Ppisar| Petr Písař]]
* Email: <ppisar(a)redhat.com>
=== Completed Items ===
=== Items in Progress ===
=== Items to Be Done ===
* Upstream to release Perl 5.30
* Get dedicated build-root from rel-engs (''f31-perl'')
* Define perl_bootstrap in perl-srpm-macros
* Rebase perl to 5.30.0
* Build new perl 5.30 keeping old COMPAT Provides
* 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
* Remove old perl(:MODULE_COMPAT_5.28.*) from perl
* Undefine perl_bootstrap
* Rebuild other packages: Use Fedora::Rebuild dependency solver
* Rebuild packages having perl_bootstrap condition in spec file
* Rebuild all updated packages
* Merge dedicated build-root to rawhide and remove the dedicated one by rel-engs
* Synchronize packages upgraded in ''f31'' build root
* Rebuilt Perl packages: 0 of 3186 done (0.00 %)
* Failed builds (0):
* Unsatisfied dependencies (0):
== Detailed Description ==
New perl is released every year and updates containing mainly bug
fixes follow during the year. The 5.30.0 version is stable release
this year.
In addition, Perl ''site'' paths will be made ABI-specific. CPAN
modules intended for an installation under /usr/local/ will be
installed to /usr/local/{share,lib*}/perl5/5.30 paths. This will
prevent from breaking Perl with old locally installed modules after a
Fedora upgrade.
== 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 ''f31-perl''
build-root against perl 5.30.0 and then if no major problem emerges
the packages will be merged back to ''f31'' build-root.
* Proposal owners:
New perl and all packages requiring perl or a Perl module will be
rebuilt into ''f31-perl'' build-root.
* Other developers: 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/issue/8368 #8368] (a
check of an impact with Release Engineering is needed)
Release engineers will be asked for new ''f31-perl'' build-root
inheriting from ''f31'' build-root. After successful finishing the
rebuild, they will be asked to merge ''f31-perl'' packages back to
''f31'' build-root.
* Policies and guidelines:
No policies have to be modified to complete this change.
== Upgrade/Compatibility Impact ==
Vast majority of functionality will be preserved. Only the packages
that failed to build against perl 5.30 will be removed from the
distribution. That will require to remove those packages from existing
systems otherwise package manager will encounter unsatisfied
dependencies. Modules installed locally into /usr/local will become
unavailable and users will need to reinstall them.
== How to Test ==
Try upgrading from Fedora 30 to 31. 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 reinstalation.
== Dependencies ==
There is more than 3100 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 ==
If we find perl 5.30 is not suitable for Fedora 31, we will revert
back to perl 5.28 and we drop the temporary build-root with already
rebuilt packages.
* Contingency deadline: branching Fedora 31 from Rawhide.
* Blocks release? No.
== Documentation ==
* [https://metacpan.org/pod/release/XSAWYERX/perl-5.30.0-RC1/pod/perldelta.pod
5.30.0 perldelta]
* An announcement on the perl-devel mailing list
* [https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraprojec…
Making Perl site paths ABI-specific] discussion on perl-devel mailing
list
== Release Notes ==
=== Important Changes ===
* Unicode 11, 12 and draft 12.1 is supported
* The upper limit "n" specifiable in a regular expression quantifier
of the form "{m,n}" has been doubled to 65534
* Wildcards in Unicode property value specifications are now partially supported
* qr'\N{name}' is now supported
* It is now possible to compile perl to always use thread-safe locale
operations.
* Limited variable length lookbehind in regular expression pattern
matching is now experimentally supported
* Use faster method to convert to UTF-8
* Turkic UTF-8 locales are now seamlessly supported
* Eliminate opASSIGN macro usage from core
* -Drv now means something on -DDEBUGGING builds
=== Removed Features and Incompatible Changes ===
* Removed modules: Math::BigInt::CalcEmu, arybase, Locale::Code, B::Debug
* Pattern delimiters now must be graphemes
* Delimiters must now be graphemes
* Some formerly deprecated uses of an unescaped left brace "{" in
regular expression patterns are now illegal
* Assigning non-zero to $[ is fatal
* Previously deprecated sysread()/syswrite() on :utf8 handles now fatal
* my() in false conditional prohibited
* Fatalize $* and $#
* Fatalize unqualified use of dump()
* Remove File::Glob::glob()
* pack() no longer can return malformed UTF-8
* Any set of digits in the Common script are legal in a script run of
another script
* JSON::PP enable allow_nonref by default
* Site paths moved from /usr/local/…/perl5 to /usr/local/…/perl5/5.30
=== Deprecated Features ===
* In XS code, use of various macros dealing with UTF-8.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
https://fedoraproject.org/wiki/Changes/DisableRootPasswordLoginInSshd
== Summary ==
The upstream OpenSSH disabled password logins for root back in 2015.
The Fedora should follow to keep security expectation and avoid users
surprises with this configuration.
== Owner ==
* Name: [[User:jjelen| Jakub Jelen]], OpenSSH maintainer
* Email: jjelen(a)redhat.com
== Detailed Description ==
The OpenSSH server configuration contains a configuration option
`PermitRootLogin`, which controls whether the root user is allowed to
login using passwords or using public key authentication. The root
login is target of most of the random or targeted attack on Linux
systems and password is usually the weakest part. For that reason, the
upstream OpenSSH changed this option in 2015 to `prohibit-password`,
which still allows public-key authentication, but prevents the
password logins. Fedora was for many practical reasons keeping the old
configuration since then, but the difference is no longer bearable and
might confuse users expecting the root logins will not be enabled out
of the box.
On the other hand, there is still a lot of infrastructure, installers
and test instances that simply might depend on this configuration and
therefore this change needs to go through the system-wide change so
everyone is onboard.
== Benefit to Fedora ==
This will provide more secure Fedora installations out of the box and
prevent inadvertently accessible root logins in the wild.
== Scope ==
* Proposal owners: Modify the default shipped sshd configuration in
`sshd_config` to no longer include the `PermitRootLogin yes` option
and advertise this change throughout Fedora.
* Other developers: Make sure their workflow does not include logging
in as a root to ssh, otherwise modify that workflow
* Release engineering: [https://pagure.io/releng/issues/8342]
* Policies and guidelines: none
* Trademark approval: none
== Upgrade/compatibility impact ==
The updates of previously-modified `sshd_config` will not be affected
and create a `.rpmnew` configuration file.
The updates of default `sshd_config` will be updated and the
modification needs to be listed in release notes to prevent surprises.
== How To Test ==
* Make sure you have root user with password and you can login to this
user using `su`
* Make sure the sshd_config does not contain `PermitRootLogin yes` option
* Restart sshd service: `systemctl restart sshd`
* Try to connect to root user: `ssh
-oPreferredAuthentications=password root@localhost`
* Should fail
Other authentication methods (publickey, gssapi should not be affected)
== User Experience ==
Nothing in production should really depend on root password logins in
2019. If it does, it is the time to change that (or explicitly allow
it on the affected systems).
== Dependencies ==
Installer and kickstarts depending on this functionality.
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) Maintainer
will revert the change to sshd_config if needed.
* Contingency deadline: Beta freeze
* Blocks release? no
* Blocks product? no
== Documentation ==
OpenSSH in Fedora 31 does not allow root logins using passwords by default.
Upstream release notes: http://www.openssh.com/txt/release-7.0
== Release Notes ==
OpenSSH in Fedora 31 does not allow root logins using passwords by default.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
https://fedoraproject.org/wiki/Changes/MingwEnvToolchainUpdate
== Summary ==
Update the MinGW base environment and toolchain to the latest upstream
stable releases.
== Owner ==
* Name: [[User:smani|Sandro Mani]]
* Email: manisandro(a)gmail.com
== Detailed Description ==
The following packages will be updated
* mingw-gcc to version 9.1.0
* mingw-w64-tools to version 6.0.0
* mingw-winpthreads to version 6.0.0
* mingw-crt to version 6.0.0
* mingw-headers to version 6.0.0
* mingw-binutils to version 2.32
Packages for early testing are available here:
https://copr.fedorainfracloud.org/coprs/smani/mingw-gcc9/builds/
== Benefit to Fedora ==
Ship the latest available MinGW environment and GNU toolchain.
== Scope ==
* Proposal owners:
The above mentioned packages will be updated. Build failures following
the mass rebuild will be inspected.
* Other developers:
Help with build failures may be requested.
* Release engineering: Impact check [https://pagure.io/releng/issues/8340]
* Release engineering: Mass rebuild requested
* Policies and guidelines: No policies need to be changed
== Upgrade/compatibility impact ==
No impact
== How To Test ==
Update the system once the updated packages land, look out for new
build failures etc.
== User Experience ==
The features of the newest MinGW environment and GNU Toolchain will be
available to the users.
== Dependencies ==
None
== Contingency Plan ==
* Contingency mechanism: Revert to older versions of environment /
toolchain, mass rebuild mingw packages again
* Contingency deadline: Before release
* Blocks release? Yes
* Blocks product? No
== Documentation ==
* http://gcc.gnu.org/gcc-9/
* https://mingw-w64.org/doku.php/versions
== Release Notes ==
Fedora 31 comes with the mingw-w64-6.0.0 environment, mingw-gcc-9.1
and mingw-binutils 2.32.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
Today we are starting the Nomination & Campaign period during which we
accept nominations to the "steering bodies" of the following teams:
* FESCo (Engineering) (4 seats) [1]
* Fedora Council (1 seat) [2]
* Mindshare (1 seat) [3]
This period is open until 2019-05-22 at 23:59:59 UTC.
Candidates may self-nominate. If you nominate someone else, please
check with them to ensure that they are willing to be nominated before
submitting their name.
The steering bodies are currently selecting interview questions for
the candidates.
Nominees submit their questionnaire answers via a private Pagure
issue. The Election Wrangler or their backup will publish the
interviews to the Community Blog before the start of the voting
period. Fedora Podcast episodes will be recorded and published as
well.
Please note that the interview is mandatory for all nominees. Nominees
not having their interview ready by end of the Interview period
(2019-05-29) will be disqualified and removed from the election.
As part of the campaign people may also ask questions to specific
candidates on the appropriate mailing list.
The full schedule of the elections is available on the Elections
schedule[4]. For more information about the elections process, see the
wiki[5].
[1] https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations
[2] https://fedoraproject.org/wiki/Council/Nominations
[3] https://fedoraproject.org/wiki/Mindshare/Nominations
[4] https://fedorapeople.org/groups/schedule/f-30/f-30-elections.html
[5] https://fedoraproject.org/wiki/Elections
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
Fedora 28 will be EOL on Tuesday, May 28th, 2019. On this day we are
going to close all of the Fedora 28 bugs which remain open [1].
You have a few weeks remaining to submit updates, if you have any,
before the Fedora 28 release becomes unsupported.
[1] https://fedoraproject.org/wiki/Releases/30/HouseKeeping#Fedora_28_EOL_Closu…
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
Pronouns: he/him