There will be an outage starting at 2019-11-20 22:00 UTC, which will last approximately 1 hour.
To convert UTC to your local time, take a look at
date -d '2019-11-20 22:00 UTC'
Reason for outage:
We will be updating the koji hub to version 1.19.1, including database schema update.
Additionally we will be adding a patch to allow livemedia to compose in rawhide
with the latest lorax version.
Appologies for the short notice of this outage.
koji - https://koji.fedoraproject.org/koji
Ticket Link: https://pagure.io/fedora-infrastructure/issue/8399
Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above.
== Summary ==
Add freeze (similar to [[Milestone_freezes|beta or final freeze]])
after new Fedora is branched. This freeze will be removed as soon as a
branched compose is ready.
== Owner ==
* Name: [[User:jkonecny| Jiří Konečný]]
* Email: jkonecny(a)redhat.com
* Name: [[User:churchyard| Miro Hrončok]]
* Email: mhroncok(a)redhat.com
* Name: [[User:Kevin| Kevin Fenzi]] (nirik)
* Email: kevin(a)scrye.com
== Detailed Description ==
For basically every branching of Fedora there is a gap between the
branching date and when the first branched compose is created. This
gap is most of the time not that problematic because it's just a few
days but it could be a lot longer given bad circumstances. For Fedora
31, the first branched compose was available only a week before the
Having a finished compose late introduces a plenty of problems for
projects which need to test on the newer compose. Not having the
compose will result in testing in Rawhide, however the longer is the
gap between branching and compose the more diverged Rawhide and
branched Fedora are. Package updates are not available on branched
before a compose is ready.
For example, in case of Fedora 31 branching Rawhide (Fedora 32)
adapted a new Python version sooner than the compose for the Fedora 31
was available. So tests were running with the new Python version
showing errors not related to the branched Fedora.
This change will help to avoid problems described above in the future
for new branched Fedoras. It will help Release Engineering to
concentrate on issues blocking compose and avoid having to solve new
problems introduced by package updates.
== Benefit to Fedora ==
This change should help to make the gap between branching date and
when the compose is ready shorter. It should help teams to stay
focused on fixing the compose instead of making new features.
== Scope ==
* Proposal owners: Create a wiki page describing this freeze
* Other developers: Release Engineers have to create and/or adjust
koji targets and tags after branching. They will make the adjustments,
but disable some part of the workflow. Either collect packages in the
tag to be signed, or collect them in the tag to be autosubmitted to
gating by bodhi. Then, once a compose is done, restart that process
and process the backlog. If a package is needed for a fix, it can
manually be tagged in.
* Release engineering: [https://pagure.io/releng/issue/9014 #9014]
* Policies and guidelines: Fedora wiki page about freeze process
should change appropriately.
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
== How To Test ==
After Fedora is branched, new package updates are not getting into
compose if not tagged by Release Engineers explicitly, until a compose
== User Experience ==
Users should have compose of the branched Fedora sooner. This also
makes package updates sooner to land.
== Dependencies ==
== Contingency Plan ==
* Contingency mechanism: Release Engineering will use the old stable
steps used for older Fedoras.
* Contingency deadline: Decision of Release Engineering.
== Documentation ==
Mailing thread https://firstname.lastname@example.org...
He / Him / His
Fedora Program Manager
Today we are starting the Nomination & Campaign period during which we
accept nominations to the "steering bodies" of the following teams:
* FESCo (Engineering) (5 seats) 
* Fedora Council (1 seat) 
* Mindshare (1 seat) 
This period is open until 2019-11-13 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
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
Please note that the interview is mandatory for all nominees. Nominees
not having their interview ready by end of the Interview period
(2019-11-20) 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. For more information about the elections process, see the
program management docs.
He / Him / His
Fedora Program Manager
A fonts packaging policy rewrite proposal has been pushed to FPC today:
It should be clearer, more opinionated, and take into account:
– updates of The OpenType standard
– variable fonts
– web fonts
– upstream depreciation of non OpenType formats: final stages of the
Harfbuzz consolidation decided at the 2006 Text Layout summit
– appstream & fonts
– weak dependencies
– and probably more I forget here
It is based on the new fonts-rpm-macros project for automation:
This project builds on tooling enhancements in redhat-rpm-config and
rpm itself, done during the past two years for the Forge and Go sets of
packaging macros. It started 2 years ago as a fork of fontpackages,
which is the core of our current fonts packaging guidelines.
It will require putting the fonts-srpm-macros package in the default
build root, like is done for other domain-specific packaging macro
– better documentation (clearer and more complete)
– better automation (less packager hassle for better and more complete
– tools and scripts
– fixing metadata with ttname
Mostly because no one seems willing to maintain those scripts, or port
ttname to python 3.
showcases the new policy on 62 real-world source packages. Some of
those are badly delayed updates to Fedora packages, others are brand-new packages ready for Fedora inclusion. They include major font packages such as Stix, DejaVu, Droid, IBM Plex.
Existing Fedora packages will continue to build, the old fontpackages
macros are grandfathered in fonts-rpm-macros for now. They will be
removed in a few years to give packagers time to apply the new