On Tue, Jul 25, 2023 at 3:58 PM Fabio Valentini <decatho...@gmail.com> wrote:
>
> As far as I can tell, the toolchain proposal was announced on the devel / 
> devel-announce lists on July 7 but never submitted to FESCo for a vote. Looks 
> like the process broke down somewhere along the way.

I think it was actually a couple of days before that, but no matter.
In either case it was announced more than a week after it was
submitted (which happened to be the date of the deadline). So the
problem is two-fold:

1. It sat in "ChangeReadyForWrangler" for a week during a rather
time-critical part of the cycle
2. It never made it to FESCo

I could be salty about this, but I'll refrain. The point is that
altering the schedule wouldn't make a difference here because the
schedule isn't the problem. It's that there's not someone whose actual
job is wrangling Change proposals. amoloney has done a great job
picking up many of my former duties while also doing her full time
job, but as that sentence implies, there are capacity issues. Of
course, earlier submission is better when possible but I don't know if
it was possible in this case and it's not clear it would have helped
this specific issue.

-- 
Ben Cotton (he/him)
TZ=America/Indiana/Indianapolis
https://fedoraproject.org/wiki/User:Bcotton
_______________________________________________
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