From 6574bff9657059c31f635891e755f640abbf8b24 Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Jan 30 2024 08:50:15 +0000 Subject: [PATCH 1/3] updates policy: add blanket exception for rust -devel packages Requested in https://pagure.io/fesco/issue/2474#comment-689063, approved in https://pagure.io/fesco/issue/2474#comment-694322. Resolves https://pagure.io/fesco/fesco-docs/issue/57. --- diff --git a/fesco/modules/ROOT/pages/Updates_Policy.adoc b/fesco/modules/ROOT/pages/Updates_Policy.adoc index db3da41..aece853 100644 --- a/fesco/modules/ROOT/pages/Updates_Policy.adoc +++ b/fesco/modules/ROOT/pages/Updates_Policy.adoc @@ -315,8 +315,9 @@ Some classes of software will not fit in these guidelines. If your package does the classes below, but you think it should be allowed to update more rapidly, propose a new exception class to FESCo and/or request an exception for your specific update case. -Note that you should open this dialog BEFORE you build or push updates. In the event that an issue -is raised in the middle of an update already in progress, make sure you turn off autokarma pushes — +Note that you should open this dialog **before** you build or push updates. +In the event that an issue is raised in the middle of an update already in progress, +make sure you turn off autokarma pushes — this can be done while the update is pending in Bodhi. The following things would be considered in a exception request. @@ -344,6 +345,12 @@ Things that would make it less likely to grant a request: The following packages have been granted exceptions for the following reasons: +[[rust]] +===== Rust -devel packages +This exception covers all Rust -devel packages, i.e. rpms with Rust sources. +Those packages are used to build packaged Rust binaries +and are not directly usable by users. + [[kernel-package]] ===== kernel package From af0c8c8ca233cc0e9daa4080b4967cbaad489703 Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Feb 02 2024 16:15:13 +0000 Subject: [PATCH 2/3] Add requirement to retitle FastTrack requests with [FastTrack] This was voted and approved in the meeting 2024-01-29: FastTrack tickets must gain a [FastTrack] title addition and if they have not received enough votes in 48 hours, a FESCo member should send a reminder. APPROVED (+6, 0, 0) --- diff --git a/fesco/modules/ROOT/pages/index.adoc b/fesco/modules/ROOT/pages/index.adoc index 6f68ecc..a55cb88 100644 --- a/fesco/modules/ROOT/pages/index.adoc +++ b/fesco/modules/ROOT/pages/index.adoc @@ -100,6 +100,10 @@ If there are no votes at all, the proposal is considered rejected and the status quo will be maintained. The submitter may at this time make a new proposal which will be processed following the usual rules. +Tickets which are labeled as "Fast Track" must be retitled to include "[FastTrack]" +and if they have not received enough votes in 48 hours, +a FESCo member should send a reminder. + [[meeting-votes]] == Meeting Votes From 686a7edda3fd76b253776256c6860fc83fc62002 Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Feb 02 2024 16:32:30 +0000 Subject: [PATCH 3/3] Fix typo --- diff --git a/fesco/modules/ROOT/pages/index.adoc b/fesco/modules/ROOT/pages/index.adoc index a55cb88..940fc1d 100644 --- a/fesco/modules/ROOT/pages/index.adoc +++ b/fesco/modules/ROOT/pages/index.adoc @@ -25,7 +25,7 @@ Issues FESCo handles include: * Responsible for what software is offered to end users under what conditions. * Oversight and approval of new spins and other media that doesn't fit under a working group. -FESCo has empowered the FPC (Fedora Packaging Comittee) to handle management of packaging guidelines, +FESCo has empowered the FPC (Fedora Packaging Committee) to handle management of packaging guidelines, so those items are usually deferred to them with occasional FESCo oversight. Candidates for FESCo should be people who have a wide breadth of knowledge about the Fedora Project as a whole