Friday's Fedora Facts: 2021-35

Originally published at: Friday's Fedora Facts: 2021-35 – Fedora Community Blog

Here’s your weekly Fedora report. Read what happened this week and what’s coming up. Your contributions are welcome (see the end of the post)!

I have weekly office hours on Wednesdays in the morning and afternoon (US/Eastern time) in #fedora-meeting-1. Drop by if you have any questions or comments about the schedule, Changes, elections, or anything else. See the upcoming meetings for more information.



Conference Location Date CfP
PackagingCon virtual 9–10 Nov closes 4 Sept
CentOS Dojo virtual 7–8 Oct closes 6 Sept
Ohio Linux Fest Columbus, OH, US early Dec closes 1 Oct
DevConf.CZ Brno, CZ & virtual 28–29 Jan closes 24 Oct
SCaLE Pasadena, CA, US 5–8 Mar closes 30 Nov

Help wanted

Upcoming test days

Prioritized Bugs

Bug ID Component Status
1949712 selinux-policy POST

Upcoming meetings


Release open bugs
F33 5208
F34 4715

Fedora Linux 35


  • 2021-09-14 — Beta release early target
  • 2021-09-21 — Beta release target #1

For the full schedule, see the schedule website.


See the ChangeSet page or Bugzilla for information on approved Changes.

BZ Status Count
ON_QA 41


Bug ID Component Bug Status Blocker Status
1993238 distribution ON_QA Accepted (Beta)
1995817 gnome-software ON_QA Accepted (Beta)
1998681 kde-settings MODIFIED Accepted (Beta)
1989726 mutter NEW Accepted (Beta)
1999321 freeipa NEW Proposed (Beta)

Fedora Linux 36


Have something you want included? You can file an issue or submit a pull request in the fedora-pgm/pgm_communication repo.

1 Like

One thing I did differently this week is to include a count of open bugs for the supported releases (F33 and F34). A few weeks ago, I started including bug counts for development releases. So my question is where should I put the bug counts for the in-development releases?

  • In the table with the supported releases
  • With the other information specific to that release
  • Both of the above
  • I don’t care

0 voters