Uploaded August 2026 | Updated September 2026, 27 seconds ago
RHEL Schedule Design Discussion
This is an auto-generated summary of the FRCL call on 2026-01-14:
Brendan Conoboy confirmed the recorded session with Fedora and CentOS distribution leads regarding the continually evolving Red Hat Enterprise Linux (RHEL) schedule, which transitioned from an unpredictable schedule to a clockwork one, followed by a re-architected schedule to streamline development by increasing the development period and eliminating the minor release beta in favor of CentOS Stream as the public snapshot. Brendan Conoboy, Aleksandra Fedorova, and Neal Gompa (Conan Kudo) discussed the purpose of Internal Target Milestones (ITMs) to improve predictability and guidance for external contributions, with Brian Stinson clarifying that the best approach for contributors is to directly communicate with component maintainers due to varied testing requirements. Brian Stinson, Pat Riehecky, and Yaakov Selkowitz agreed that filing a Jira ticket is the correct community interface for contributions, which Brendan Conoboy noted auto-assigns the RHEL maintainer for better communication, while Troy Dawson and Carl George addressed the challenge of the private source code "cut over" date for minor releases, advising external projects like EPEL to utilize public hints and contribute changes early.
Jira Epic: redhat.atlassian.net/browse/FRCL-5
Gemini AI Summary: docs.google.com/document/d/1VMxPGpghhrrd5sCje-lQv-QZH1OrFVMZq9HG5HnsREI/edit?usp=meet_tnfm_calendar
RHEL Schedule Design Discussion
This is an auto-generated summary of the FRCL call on 2026-01-14:
Brendan Conoboy confirmed the recorded session with Fedora and CentOS distribution leads regarding the continually evolving Red Hat Enterprise Linux (RHEL) schedule, which transitioned from an unpredictable schedule to a clockwork one, followed by a re-architected schedule to streamline development by increasing the development period and eliminating the minor release beta in favor of CentOS Stream as the public snapshot. Brendan Conoboy, Aleksandra Fedorova, and Neal Gompa (Conan Kudo) discussed the purpose of Internal Target Milestones (ITMs) to improve predictability and guidance for external contributions, with Brian Stinson clarifying that the best approach for contributors is to directly communicate with component maintainers due to varied testing requirements. Brian Stinson, Pat Riehecky, and Yaakov Selkowitz agreed that filing a Jira ticket is the correct community interface for contributions, which Brendan Conoboy noted auto-assigns the RHEL maintainer for better communication, while Troy Dawson and Carl George addressed the challenge of the private source code "cut over" date for minor releases, advising external projects like EPEL to utilize public hints and contribute changes early.
Jira Epic: redhat.atlassian.net/browse/FRCL-5
Gemini AI Summary: docs.google.com/document/d/1VMxPGpghhrrd5sCje-lQv-QZH1OrFVMZq9HG5HnsREI/edit?usp=meet_tnfm_calendar
