On Thu, 2006-07-27 at 11:11 -0700, Richard Fish wrote: > On 7/27/06, Chris Gianelloni <[EMAIL PROTECTED]> wrote: > Please don't interpret my original message as a complaint. It isn't. > It is mostly a question of the process. My understanding of > stabilization bugs was that they should be the exception, not the > rule... > > > that you might not be able to make a commitment, or even want to do so. > > However, every single bug report that you file *is* helping out... and > > every little bit helps. > > ...and I was wrong.
The x86 architecture team (as well as some others) do not mark packages stable unless there is a bug. In the case of the x86 team, it is simply due to a lack of manpower and also due to our feelings that we should not mark things stable without the maintainer requesting it. Of course, we don't *require* a bug report be made. If the maintainer asks (via email, IRC, etc.) us, then we will do it. Also, we don't require that requests originate from the maintainer, only that the maintainer approves. For example, I, as a user, could file a request to have a package marked stable, this would be assigned to the maintainer. If the maintainer agrees, then the arch teams are added to CC on the bug and they mark the package stable. Many packages do not get marked stable simply because most developers maintain a very large number of packages, and simply forget. This is why bug reports from the users is definitely helpful in getting things stable. -- Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part
