| |
@@ -283,11 +283,11 @@
|
| |
* Anybody opens a bugzilla requesting a package be added to EPEL-X. A
|
| |
packager (the bugzilla reporter or another person) expresses that they
|
| |
are willing to help maintain / co-maintain that package in EPEL-X.
|
| |
- * A week goes by with no response
|
| |
+ * A week goes by with no action
|
| |
* They re-say that they are willing to maintain / co-maintain the
|
| |
package in EPEL
|
| |
** This is just incase the initial message was missed.
|
| |
- * A week goes by with no response
|
| |
+ * A week goes by with no action
|
| |
* They file a https://pagure.io/releng/issues/[rel-eng ticket], that
|
| |
points to the bugzilla, requesting appropriate privileges to be able to
|
| |
branch and build that package in EPEL-X
|
| |
@@ -298,6 +298,13 @@
|
| |
* They then request a branch, and build the package in EPEL-X following
|
| |
normal steps.
|
| |
|
| |
+ "Action" is considered something that progresses the bug.
|
| |
+ "Action" can be positive or negative. Such as a response of "The code
|
| |
+ has not been updated for 10 years and has security issues" and then they
|
| |
+ close the ticket.
|
| |
+ "No Action" could be no response at all, or it could be a response of
|
| |
+ "I do not want to do epel" and then they do nothing else.
|
| |
+
|
| |
[[distribution_specific_guidelines]]
|
| |
== Distribution specific guidelines
|
| |
|
| |
tdawson
commented 2 years ago
The current Stalled EPEL Requests policy says "A week goes by with no response" but it is possible (and has happened) that a package is still stalled, even with a response.
This update clarifies better what a stalled package is.
Signed-off-by: Troy Dawson tdawson@redhat.com