Approved by the Gentoo Council on 15 September 2005.
+This GLEP originated from a rather contentious discussion [1] on gentoo-dev about combining the x86 and amd64 keywords. This GLEP attempts to get at the heart of that discontent. The proposed stable-keyword guidelines have been lifted verbatim from The Doc [2].
It is time for x86 to no longer be an exception to the standard keywording guidelines. Thus, an x86 arch team should be responsible for moving packages from ~x86 to x86.
The original, informal x86 keywording policy, where almost any x86 dev (which were the vast majority of devs) who used a package could mark it stable, arose from a time when there were relatively few Gentoo devs. Adding packages to @@ -102,9 +107,9 @@ benefit x86 as well.
For a package to move to stable, the following guidelines must be met:
A robust x86 arch team needs to be created. The x86@gentoo.org alias already exists, and it merely needs to be used. This team, with the aid of potential non-dev arch testers, has the responsibility of stabling all x86 packages. @@ -130,7 +135,7 @@
There will be a considerable one-time cost involved in establishing a robust x86 arch team--a good number of bodies (the amd64 atch team has 19 active devs and 12 active non-dev arch testers) need to be recruited to be part of the @@ -158,13 +163,13 @@
Creation of a robust x86 team is already underway. The more vital step is the official change in policy, along with a sustained effort to get existing x86 devs to go along with it.
Stuart [4] has suggested the creation of a new arch keyword: "[-]maint", which would exist in tandem with the normal arch keywords, thereby making the package maintainer's intention explicit. Ciaranm has responded that by @@ -185,11 +190,11 @@ the support burden for that package.