Re: [gentoo-dev] [RFC] Reworking package stabilization policies

[Maciej Mrozowski]

On Sunday 28 of March 2010 09:39:18 Ciaran McCreesh wrote:

> > It's really freaking silly to wait months for stabilization of some
> > random php/perl library that's known to work.

> How do you know it works if you don't test on the arch in question?
The problem is not waiting for some <instert some exotic arch here> to go 
stable so it would be possible to close bug and ignore arches.
It's not about closing bug at all.
The only inconvenience from exotic arches lagging is inability to remove 
particular old ebuild from tree, that's it.

It's about having package marked stabled on my arch (amd64 in my case, may be 
other from other developer's perspective) in a timely manner.

And I know it works on my arch because I test it and often use it on daily 
basis.

On Sunday 28 of March 2010 13:32:59 Richard Freeman wrote:
> amd64 has had the policy that any dev can stabilize if they've tested it
> on a stable amd64 system, and this hasn't really caused problems.
That would have certainly solved the problem if that policy was written and 
published anywhere.

-- 
regards
MM