On Thu, 2023-10-12 at 15:04 +0200, Fabio Valentini wrote:
> On Thu, Oct 12, 2023, 14:58 Major Hayden <ma...@mhtx.net> wrote:
> 
> > Hello there,
> > 
> > I'm not able to find any items in the FESCo Pagure queue that need
> > discussion today, so I'll cancel this week's meeting and we can regroup
> > next week on October 19 at 1700 UTC.
> > 
> > Unless anyone is super excited to be the chair for next week's meeting, I
> > will do it. 🪑
> > 
> > I hope everyone has a great rest of the week and weekend! 👋
> > 
> 
> Beware that there are some change proposals that are either pending
> announcement / discussion / creation of fesco tickets. That also might be
> the reason why our Ticket queue looks kind of empty.

Well, AFAICS there are four awaiting announcement, but those wouldn't
require any FESCo action immediately. There are only two that have been
announced and not yet sent to FESCo -
https://fedoraproject.org/wiki/Changes/Drop_Sshd_Socket and
https://fedoraproject.org/wiki/Changes/KDE_Plasma_6 - and I believe we
(Aoife and I) were kinda sitting on those for Reasons: the Plasma 6 one
is a big one that still had active discussion ongoing till fairly
recently, and it seems reasonably likely that the sshd socket one won't
be needed once
https://github.com/systemd/systemd/pull/29159#issuecomment-1714205320
lands in Fedora, so we were kind of intentionally leaving it in limbo,
I think.
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
https://www.happyassassin.net



_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to