| 1 |
On Thu, Aug 4, 2016 at 6:24 PM, William Hubbs <williamh@g.o> wrote: |
| 2 |
> I can think of two ways we can improve our situation. |
| 3 |
> |
| 4 |
> We can allow maintainers to stabilize new versions of certain types of |
| 5 |
> packages on all arches where there is a previous version of the package stable |
| 6 |
> without filing stable requests. This would take a significant load off |
| 7 |
> of the arch teams. |
| 8 |
> |
| 9 |
> For packages that do not fit the first group, we could require stable |
| 10 |
> requests, but allow maintainers to stabilize the new versions after a |
| 11 |
> timeout (I would propose 30 days). |
| 12 |
> |
| 13 |
> What do folks think? |
| 14 |
|
| 15 |
I very much agree that there's a problem. Interestingly, for the |
| 16 |
stable requests I file, it seems that e.g. alpha does better than |
| 17 |
amd64 right now, thanks to having a very dedicated arch team. |
| 18 |
|
| 19 |
It makes a lot of sense to me to allow maintainers to stabilize |
| 20 |
packages after 30 days or so at least if there is a previous stable |
| 21 |
version. |
| 22 |
|
| 23 |
Cheers, |
| 24 |
|
| 25 |
Dirkjan |
Archives