On 05/22/13 11:43, Michael Palimaka wrote: > On 22/05/2013 19:22, viv...@gmail.com wrote: >> On 05/21/13 23:38, Andreas K. Huettel wrote: >>> Am Dienstag, 21. Mai 2013, 15:38:44 schrieb Thomas Sachau: >>>> And if a maintainer is not responding within 30 days, you can ping him >>>> or, without a response, try to get a different maintainer. Just >>>> assuming >>>> that a stable request is ok without a maintainer response is really >>>> not >>>> a good idea. >>> If none of the listed maintainers responds to a bug in 30 days in >>> any way, the >>> package is effectively unmaintained. >>> >> And thus its risky to mark it stable. >> >> > That's why we have arch teams in the first place, to test beforehand. > > The risky part is about the after, not the before, to avoid the risks arch teams should keep the package working *after* it has stabilized. Seem to be a good case for those things that need to be evaluated case by case and could not be written in stone.
- Re: [gentoo-dev] robo-stable b... Markos Chandras
- Re: [gentoo-dev] robo-stab... Alexis Ballier
- Re: [gentoo-dev] robo-stab... Paweł Hajdan, Jr.
- Re: [gentoo-dev] robo-stab... Andreas K. Huettel
- Re: [gentoo-dev] robo-stab... Alexis Ballier
- [gentoo-dev] Re: robo-stab... Ryan Hill
- Re: [gentoo-dev] robo-stable b... Thomas Sachau
- Re: [gentoo-dev] robo-stable bugs Andreas K. Huettel
- Re: [gentoo-dev] robo-stable b... viv...@gmail.com
- [gentoo-dev] Re: robo-stab... Michael Palimaka
- Re: [gentoo-dev] Re: robo-... viv...@gmail.com
- [gentoo-dev] Re: robo-stab... Michael Palimaka
- Re: [gentoo-dev] Re: robo-... Thomas Sachau
- [gentoo-dev] Re: robo-stab... Michael Palimaka
- Re: [gentoo-dev] Re: robo-... viv...@gmail.com
- Re: [gentoo-dev] Re: robo-... Ian Stakenvicius
- Re: [gentoo-dev] Re: robo-... Jeroen Roovers
- Re: [gentoo-dev] Re: robo-... Ian Stakenvicius
- Re: [gentoo-dev] Re: robo-... Ian Stakenvicius
- Re: [gentoo-dev] robo-stab... Rich Freeman
- Re: [gentoo-dev] robo-stable bugs Rick "Zero_Chaos" Farina