Search results

* A fully updated [https://jforbes.fedorapeople.org/testweek/ F35 test day image ] or Fedora 34 or 35 Workstation/Server installation, either ...lation from [https://koji.fedoraproject.org/koji/buildinfo?buildID=1941849 F35 koji] (see below) or [https://copr.fedorainfracloud.org/coprs/jforbes/kerne

** Merge side-tag into rawhide prior to the f35 branch date. ** Continue packaging newer release candidates into rawhide and f35 until the final release is complete (Late September 2021)

...issues with packaging and for issues that need tracking (blocker bugs for F35): [https://bugzilla.redhat.com Red Hat Bugzilla] under "IoT".

...release announcement] and the [https://docs.fedoraproject.org/en-US/fedora/f35/release-notes/ Fedora Linux 35 release notes] for specific information abou {{Common bugs issue|f35-rpi-vc4|Raspberry Pi 4 GUI frequently locks up with the Workstation Edition

* Targeted release: [[Releases/F35 | Fedora Linux 35]]

...nizations. This selection has included a filtered version of Flathub since F35, which provides access to a small number of Flathub apps. This change would Since F35, Fedora has included a Flatpak repo definition for Flathub in the fedora-fl

...-alsa, pipewire-libs, pipewire-pulseaudio...) are installed and updated to f35, but no adapter is shown in Settings nor the volume bar is shown on the Top ...delays, but was still without sound. I then tried a fresh install from the F35 Beta live image and that resulted in a nicely working VM without those issu

* A fully updated [https://jforbes.fedorapeople.org/testweek/ F35 test day image ] or Fedora 34 or 35 Workstation/Server installation, either ...lation from [https://koji.fedoraproject.org/koji/buildinfo?buildID=1855177 F35 koji] (see below) or [https://copr.fedorainfracloud.org/coprs/jforbes/kerne

* A fully updated [https://jforbes.fedorapeople.org/testweek/ F35 test day image ] or Fedora 34 or 35 Workstation/Server installation, either ...lation from [https://koji.fedoraproject.org/koji/buildinfo?buildID=1909308 F35 koji] (see below) or [https://copr.fedorainfracloud.org/coprs/jforbes/kerne

Around F35 the upstream dies. Around F37 Fedora maintainer retires the package (or orp

...leng / a koji admin required), revert mass branching script changes before f35 branch point

platform: [f35] platform: [f35]

...ourage people to really fill out all test cases. Yet we never got to it in F35. Some of the bugs might've been discovered earlier this way.

** also backport ghcX.Y's to F35, F34 [done] and later EPEL

...ed in a future kernel release, 5.12 and will hopefully be ready for F34 or F35[https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

| T14s Gen1, i7-10610U, 32 GiB Ram, initially installed under F35 and upgraded through every beta

| {{result|warn}}<ref>Not install with upgrade from F35</ref>

* Contingency deadline: F35 branch date (2021-08-10)

...ke to remove libdb in the best case in Fedora 35. And time between F33 and F35 we would like to use for discussion about solution, which could transfer ex

...ampering or data corruption. We may be able to implement this in time for F35, if this capability is deemed useful & necessary.