-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 22/05/13 06:07 AM, viv...@gmail.com wrote:
> 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.
> 

Unless it's officially maintainer-needed, a package shouldn't be in
~arch when it's unmaintained, either.  If an AT passes a package from
~arch to stable, it's no more likely to break things there than it is
in ~arch.

Plus, it's important to consider the zero-bugs case here -- if all
bugs in the ~arch package are fixed, AND the ATs give it a go, then
the likliness of harm in stable is pretty minimal.  I'd say less so
than the end-users keywording the package.


Now, one big thing I do worry about with this whole process, is that
it's going to significantly increase the workload on ATs.  And if it
does that, what's the likliness of things getting a 'pass' when they
shouldn't?  *that* part I worry about more, when the maintainer hasn't
manually cleared a package for stabilization.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlGcweYACgkQ2ugaI38ACPDGmAD/QtIKe/J5Xg3TjthITn1eTLA4
NfSMrrF6cyXfOdjtmoABAKauw9JDDX5JjUERL2K8At88VjWfeeST45qZ9HifDanv
=qB7D
-----END PGP SIGNATURE-----

Reply via email to