https://devmanual.gentoo.org/ebuild-writing/ebuild-maintenance/index.html Contains some information that are probably outdated: - Stabilization rules: SPARC: You must have prior permission from the arch lead. Usually we expect you to be on the sparc alias for QA reasons, although other arrangements can be made if you will only be working with a small group of packages. ALPHA: Maintainers may keyword their own packages but are reminded to inform the Alpha team if they can help out with testing and keywording packages so the team can keep an eye out for possible keywording mistakes. -> This should probably be dropped... I think currently nothing of this is being needed, if we *need* a package stabilized in sparc/alpha we need to CC them and let the team to act if possible. If the developer has the luck to be able to test on this arches by himself, I really doubt this arches will refuse that help - Exotic architectures (like alpha, ia64, sparc, hppa, ppc*) are short on manpower, so it's best if you avoid opening stabilization bugs for them unless it is absolutely necessary (eg, a reverse dependency for your package). More about keywording policies can be found in the keywording section. -> I would change "avoid opening stabilization bugs for them" to "avoid stabilizing new packages previously only in testing" to prevent people from wrongly not CCing arches when a new version needs stabilization AND older versions have stable keywords for this arches Thanks
I think the alpha part of this is obsolete, https://devmanual.gentoo.org/archs/alpha/index.html has a similar section, but it's a lot more general.
I think the phrasing is actually kind of confusing. I think that section actually refers to "stabilising stuff yourself", not "is it ok to CC on a bug" (and I thought it meant the latter until now).
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=17ea5e4be826a1155ddc62ce4dbbccb7d26eba15 commit 17ea5e4be826a1155ddc62ce4dbbccb7d26eba15 Author: Sam James <sam@gentoo.org> AuthorDate: 2022-01-22 23:24:54 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-02-18 18:19:34 +0000 keywording: note that stabilization rules are for actual testing These rules are for maintainers wishing to stable if they have access to hardware -- they do _not_ mean maintainers must follow these rules just to file a bug and stabilise a package via CCing arch teams (the usual route). Closes: https://bugs.gentoo.org/546942 Signed-off-by: Sam James <sam@gentoo.org> Closes: https://github.com/gentoo/devmanual/pull/267 Signed-off-by: Sam James <sam@gentoo.org> keywording/text.xml | 5 +++++ 1 file changed, 5 insertions(+)
