| 1 |
Tobias Klausmann wrote: |
| 2 |
> Hi! |
| 3 |
> |
| 4 |
> On Wed, 04 Nov 2009, Ryan Hill wrote: |
| 5 |
>> Is there any interest in allowing certain packages to be stabilized by the |
| 6 |
>> maintainer without going through the arch teams? I always feel guilty when i |
| 7 |
>> file stabilization bugs for app-doc pkgs. |
| 8 |
> |
| 9 |
> I think for bugs which only install passive files (i.e. stuff |
| 10 |
> that doesn't "power" anything else), Keywording can be done by the |
| 11 |
> maintainer. Pure doc files (like selfhtml) are in that category. |
| 12 |
> |
| 13 |
|
| 14 |
In the past when smaller arches were not that active we used to mark |
| 15 |
Java packages stable after testing by at least one arch team. The |
| 16 |
probability to find arch specific issues in something like Java is not |
| 17 |
so high so I think arrangements like this are acceptable when the arch |
| 18 |
teams have problems keeping up. |
| 19 |
|
| 20 |
Regards, |
| 21 |
Petteri |
Archives