On Fri, 2022-04-29 at 14:41 -0400, Ben Cotton wrote:
>
>
> 1. selinux-policy — https://bugzilla.redhat.com/show_bug.cgi?id=2056303 —
> ON_QA
> After upgrade to F36 several packages fail to update due to
> selinux-related errors
>
> selinux-policy updates to address this are in F34, F35, and F36
On Fri, Apr 29, 2022 at 2:41 PM Ben Cotton wrote:
>
> We are now targeting target date #2 (2022-05-10). If we slip again, we
> won't release until after the Release Party!
That should be target date #3, of course. The date is still 2022-05-10.
--
Ben Cotton
He / Him / His
Fedora Program Manager
We are now targeting target date #2 (2022-05-10). If we slip again, we
won't release until after the Release Party!
Action summary
Accepted blockers
-
1. selinux-policy — After upgrade to F36 several packages fail to
update due to selinux-related errors — ON_
Action summary
Accepted blockers
-
1. selinux-policy — gnome-initial-setup hangs when I try to setup a
google/microsoft online account — VERIFIED
ACTION: none
2. container-selinux — selinux-policy is preventing flatpak from
updating / installing / removing fl
We are currently targeting the target date #1 (2022-04-26), which
means we'd want to have blockers fixed by 18 April in order to provide
time for validation testing prior to the Go/No-go meeting on 21 April.
Action summary
Accepted blockers
-
1. kf5-kirigami2
We are currently targeting the early target date (2022-04-19), which
means we'd want to have blockers fixed by 11 April in order to provide
time for validation testing prior to the Go/No-go meeting on 14 April.
We can do it!
Action summary
Accepted blockers
-
F36 Final freeze begins Tuesday 5 April. We are currently targeting
the early target date (2022-04-19), which means we'd want to have
blockers fixed by 11 April in order to provide time for validation
testing prior to the Go/No-go meeting on 14 April.
Action summary
Accepted
F36 Beta is go, so it's time to shift to Final blockers. The Final
freeze begins on 5 April, with a target release date of 19 April.
Action summary
Accepted blockers
-
1. grub2 — Windows with bitlocker enabled can't be booted, needs to
use bootnext instead of
