Olivier Crete wrote:[Tue Jun 07 2005, 05:56:35PM EDT] > Are you sure its not a policy?
Fairly certain. It's been discussed around in circles in the past. > Because it should be and it has been > discussed before. Arch teams should NOT get ahead of the maintainer > without his permission... or if they really really know what they > are doing. Maintainers normally know their package/ebuilds and often > have very good reasons to keep a package ~arch for more than 30 > days.. Ciaran would have something to say about this, along the lines of some packages sitting idle in ~arch state because the maintainer isn't really paying attention. In that case, who can really blame an arch team for moving ahead on their own? Your statements make a lot of sense, and yes, it's how one would assume things work. But perspective can change when you're working on an architecture and losing patience with package maintainers. In practice, arch maintainers gradually learn what packages are well-maintained and what packages they stabilize without prior maintainer approval. A good example is foser's shepherding of gnome... in general the arches wait for his lead before stabilizing. Regards, Aron -- Aron Griffis Gentoo Linux Developer
pgpYXfku3HAzi.pgp
Description: PGP signature
