Dear all,
Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 29
Beta Release Readiness meeting. This meeting will be held on Thursday,
2018-09-13 at 19:00 UTC.
We will meet to make sure we are coordinated and ready for the Beta
release of Fedora 29. Please note that this meeting will be held even
if the release is delayed at the Go/No-Go meeting on the same day two
hours earlier.
You may receive this message several times in order to open this
meeting to the teams and to raise awareness, so hopefully more team
representatives will come to this meeting. This meeting works best
when we have representatives from all of the teams.
For more information, see
https://fedoraproject.org/wiki/Release_Readiness_Meetings.
I will ask for readiness from each of the teams listed below. If there
are additional teams that should be explicitly included, let me know.
All teams and contributors are welcome to provide input at the
meeting.
* Ambassadors
* Cloud WG
* Design
* Desktop
* Documentation
* Fedora Project Leader
* FESCo
* Infrastructure
* Marketing
* QA
* Release Engineering
* Server WG
* Spins
* Translations
* Websites
View the meeting on Fedocal:
https://apps.fedoraproject.org/calendar/Fedora%20release/2018/9/10/#m9337
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
https://fedoraproject.org/wiki/Changes/FreeIPA_Python_2_Removal
== Summary ==
FreeIPA 4.8 will require Python 3.6+ and therefore no longer provide
Python 2 packages on Fedora 30.
== Owner ==
* Name: Christian Heimes (cheimes)
* Email: cheimes(a)redhat.com
== Detailed Description ==
On Fedora 27 to 29, FreeIPA client and server packages use Python 3
default. Additionally FreeIPA provides Python 2 packages. The Python 2
packages are not used by FreeIPA, but are merely provided for
backwards compatibility, e.g. Python 2 applications that utilize
python2-ipaclient to communicate with a FreeIPA server.
The FreeIPA upstream project is going to drop support for Python 2.7
in the upcoming FreeIPA release 4.8.0. Python 2 support is not only
causing development and testing overhead. It's also blocking
improvements like using new python-based 389-DS installer, use of new
Python features, and more. The removal of Python 2 support was
[https://lists.fedoraproject.org/archives/list/freeipa-devel@lists.fedorahos…
announced] on the FreeIPA development on 2018-09-03.
=== Removed packages ===
* python2-ipalib
* python2-ipaclient
* python2-ipaserver
* python2-ipatests
* python2-ipa-desktop-profile-client (dependency)
== Benefit to Fedora ==
The removal of Python 2 support is in alignment with Mass Python 2
Package Removal proposal. FreeIPA depends has a large list of
dependencies. The change makes it possible to drop more Python 2
packages.
== Scope ==
* Proposal owners:
** Release FreeIPA 4.8.0 until mid January 2019
** Build and deliver FreeIPA 4.8.0 packages before 2019-01-29
** Add removed packages to ''fedora-obsolete-packages''.
* Other developers:
** Port Fleet Commander's fc-admin to Python 3 and no longer depend on
FreeIPA's Python 2 packages.
** Drop Fleet Command's Python 2 desktop profile package
** Port Ipsilion Project to Python 3 and no longer depend on FreeIPA's
Python 2 packages.
FreeIPA team is willing to help to aforementioned projects with their
port to use Python 3 FreeIPA libraries.
* Release engineering: [https://pagure.io/releng/issue/7760 #7760]
There is no releng work needed for this change.
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
The removal of Python 2 support will not affect FreeIPA server or
client systems. However 3rd party applications and scripts may be
affected. These applications and scripts must be ported to Python 3.
On upgrade from Fedora 29, previously installed ''python2-ipa*''
packages cannot be retained. All ''python[23]-ipa*'' packages have a
hard version dependency on common files with a requires line like
''Requires: freeipa-common = %{version}-%{release}''. This requires
cannot be satisfied for existing ''python2-ipa*''. Therefore
''python2-ipa*'' packages have to added to
''fedora-obsolete-packages'' package. This will ensure that the Python
2 packages are uninstalled on system upgrade.
== How To Test ==
* A fresh Fedora 30 installation will no longer have python2-ipa*
packages available.
* On upgrade from Fedora 29, all python2-ipa* packages are uninstalled.
== User Experience ==
N/A
== Dependencies ==
* fedora-obsolete-packages
* ipsilon-tools-ipa
* python2-ipa-desktop-profile-client
* fleet-commander-admin
== Contingency Plan ==
* Contingency mechanism: Keep shipping FreeIPA 4.7
* Contingency deadline: 2019-01-31
* Blocks release? No
* Blocks product? N/A
== Documentation ==
This page is the main documentation.
Also see https://pythonclock.org/ and
https://fedoraproject.org/wiki/Changes/Mass_Python_2_Package_Removal .
== Release Notes ==
FreeIPA no longer supports Python 2. All ''python2-ipa*'' packages and
''python-ipa*'' aliases are discontinued.
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
FESCo accepted [1] a new policy to handle packages with long-standing
known security bugs in a way similar to FTBFS bugs:
AGREED: If a CRITICAL or IMPORTANT security issue is currently open
against a package, or a security issue of lower severity has been
open for at least 6 months, four weeks before the branch point a
procedure similar to long-standing FTBFS will be triggered
immediately, with 8 weeks of weekly notifications to maintainers and
subsequent orphaning and then subsequent removal from distribution.
This applies to all packages, not just leaf.
This policy will apply to F30 and later. The branch point is on
2019/02/19, so somewhere around January 22 the procedure should start
with notifications being sent out. Maintainers are of course encouraged
to fix any security issues immediately. See [2] for a list of currently
open security bugs.
[1] https://pagure.io/fesco/issue/1935#comment-528180
[2] https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&…
Zbyszek,
on behalf of FESCo