Please consider the release engineering impact of this change proposal targeting Fedora 32:
Should probably also have an infrastructure ticket too due to the minimum HW requirement for x86 builders. https://pagure.io/fedora-infrastructure/new_issue
Thanks. I filed: https://pagure.io/fedora-infrastructure/issue/7968
Metadata Update from @mohanboddu: - Issue tagged with: meeting
Can I know where is the right place to raise my concerns for this change? I don't want to make a lot of noise in an improper place.
@zsun If it's not specifically a releng concern, I think you should wait until the change proposal is announced on devel-announce.
it's not directly releng related. I'll wait and reply when it's available in devel{,-announce} list.
Thanks.
I made a comment on the feature request, and provided more detail in a direct email to Florian. I'll send a copy of that to Peter shortly.
The announcement on this just went out to devel-announce, but included no feedback links other than this ticket and the infrastructure one. Can I ask what would be the correct venue to voice concerns, preferably without joining a high-volume mailing list?
@ferdnyc Sorry, the correct place to give feedback is on devel@, but you can post a reply from the web using HyperKitty: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/MPFXH4Y5LDC5L2VXWKUHAX3WAKBQXR4U/
devel@
Metadata Update from @mohanboddu: - Issue tagged with: changes, f32
No releng work is needed on this ticket.
Closing the ticket.
Metadata Update from @mohanboddu: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open) - Issue tagged with: change-noreleng