From 6a7846c567ada9fdc5a6c7ac0836c7b6c481efc8 Mon Sep 17 00:00:00 2001 From: Carl George Date: Apr 21 2022 00:49:53 +0000 Subject: Update incompat policy to match updates policy time period The current requirements for EPEL updates is one week in testing or +3 karma. Previously it was two weeks, but it was shortened. The incompatible upgrades policy should match this time period (without the karma), but it was forgotten about when the main policy was shortened. --- diff --git a/modules/ROOT/pages/epel-policy-incompatible-upgrades.adoc b/modules/ROOT/pages/epel-policy-incompatible-upgrades.adoc index 9eccd17..bcbaa78 100644 --- a/modules/ROOT/pages/epel-policy-incompatible-upgrades.adoc +++ b/modules/ROOT/pages/epel-policy-incompatible-upgrades.adoc @@ -35,7 +35,7 @@ incompatible upgrade can be built. the maintainer is responsible for sending e-mail to epel-announce announcing the incompatible upgrade and specific actions that users must take in order to continue using the software. -. Package MUST remain in testing for at least 2 weeks, regardless of +. Package MUST remain in testing for at least 1 week, regardless of received karma. In bodhi, 'Auto-request stable?' MUST NOT be checked. . When pushing the package to stable, the maintainer *MUST* send another e-mail to epel-announce. diff --git a/modules/ROOT/pages/epel-policy-updates.adoc b/modules/ROOT/pages/epel-policy-updates.adoc index 02223b7..074d640 100644 --- a/modules/ROOT/pages/epel-policy-updates.adoc +++ b/modules/ROOT/pages/epel-policy-updates.adoc @@ -28,7 +28,7 @@ stable model for this collection. Once a Enterprise Linux is released, and EPEL has left Beta and entered it's stable phase the follow applies: -* All updates MUST spend at least 1 weeks in the testing repository, or +* All updates MUST spend at least 1 week in the testing repository, or +3 karma from testers. * All updates should strive to avoid situations that require manual