| 1 |
On Mon, 10 Nov 2008 13:13:34 -0500 |
| 2 |
Mark Loeser <halcy0n@g.o> wrote: |
| 3 |
> Arch teams will normally have 30 days from the day a bug was filed, |
| 4 |
> keyworded STABLEREQ, the arch was CCed, and the maintainer either |
| 5 |
> filed the bug or commented that it was OK to stabilize (clock starts |
| 6 |
> when all of these conditions are met). |
| 7 |
|
| 8 |
30 days is a minimum, not a maximum. |
| 9 |
|
| 10 |
> If an ebuild meets the time criteria above, and there are no |
| 11 |
> technical issues preventing stabilization, then the maintainer MAY |
| 12 |
> choose to delete an older version even if it is the most recent |
| 13 |
> stable version for a particular arch. |
| 14 |
|
| 15 |
All this does is screw over users. The impact of a forced downgrade is |
| 16 |
far higher than the impact of leaving things in the tree for as long as |
| 17 |
is necessary. |
| 18 |
|
| 19 |
You are proposing giving maintainers carte blanche to screw over users |
| 20 |
and encouraging rather than reducing the kind of "us vs them" behaviour |
| 21 |
that a few package maintainers like to engage in where arch teams are |
| 22 |
treated as being in the way rather than there to help. |
| 23 |
|
| 24 |
-- |
| 25 |
Ciaran McCreesh |
Archives