On Mon, 12 May 2014 01:48:36 +0200 Jeroen Roovers wrote: > On Sun, 11 May 2014 22:25:57 +0200 > Tom Wijsman wrote: > > > This makes me question how much other such policies float around; > > especially given what was discussed at our last QA meeting regarding > > policies being spread out on the Gentoo Wiki, and other places. > > Any requirements for keywording/stabilisation *should* already be > documented on each Arch team's project page. As these are specific to > each architecture, collecting them in a single place means unnecessary > duplication and all the usual problems that tends to cause. Yes, it should; the suggestion to formalize it came up back in January: "1. I think maintainers should be able to stabilize their packages on arch's they have access to. I think this is allowed by some arch teams, but I think it would be good to formalize it." http://article.gmane.org/gmane.linux.gentoo.devel/89673 It was shortly pointed out by Sergey at some point, which might've gone lost in the length of the thread; other parts of the thread don't seem to suggest that this policy is known, and nobody questions this reply. "amd64 and x86 arch teams have agreement, that maintainers can stabilize their packages if they know how to properly test them." http://article.gmane.org/gmane.linux.gentoo.devel/89711 But now we know where this originates; so, I'll write a patch tomorrow. -- With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : TomWij@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D