public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: keywording/
Date: Sat, 25 Jan 2020 06:02:09 +0000 (UTC)	[thread overview]
Message-ID: <1579931626.b696fdc696574cd1fec19ff572c951c464fe10be.ulm@gentoo> (raw)

commit:     b696fdc696574cd1fec19ff572c951c464fe10be
Author:     Tom Wijsman <TomWij <AT> gentoo <DOT> org>
AuthorDate: Tue May 13 00:52:15 2014 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Sat Jan 25 05:53:46 2020 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=b696fdc6

keywording: Add developer stabilization exception for AMD64/X86 arches.

References:

 - "AMD64 keywording" thread by kingtaco on the gentoo-core mailing list (2007)
 - app-emacs stabilization talk by kingtaco and ulm on IRC #gentoo-dev (2007)
 - Gentoo Council agenda item: "amd64 arch team and big bug list" (2008/03/13)

Closes: https://bugs.gentoo.org/510198
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 keywording/text.xml | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/keywording/text.xml b/keywording/text.xml
index 3942138..fd8f155 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -295,6 +295,13 @@ Vulnerability Treatment Policy</uri>
 <title>Stabilization rules</title>
 <body>
 
+<p>
+AMD64, X86: If you are the maintainer of a package that currently has open bugs
+for amd64 or x86 stabilization and own the respectively amd64 or x86 hardware,
+you can do your own testing and keywording of your packages; as long as it is
+not a core system set dependency.
+</p>
+
 <p>
 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


             reply	other threads:[~2020-01-25  6:02 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-25  6:02 Ulrich Müller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-16 14:52 [gentoo-commits] proj/devmanual:master commit in: keywording/ Sam James
2022-03-14 17:07 Matt Turner
2022-03-10 23:33 Sam James
2022-02-18 18:19 Sam James
2022-01-22 21:35 Sam James
2022-01-22 21:35 Sam James
2022-01-22 21:35 Sam James
2021-10-13 13:42 Ulrich Müller
2021-10-13 13:42 Ulrich Müller
2021-07-16  9:11 Ulrich Müller
2021-07-03 16:21 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-03-30 16:10 Ulrich Müller
2021-03-11 13:16 Ulrich Müller
2021-02-17  9:29 Ulrich Müller
2021-02-17  9:29 Ulrich Müller
2021-02-17  9:29 Ulrich Müller
2021-02-17  9:29 Ulrich Müller
2021-02-15  7:21 Ulrich Müller
2020-07-12 18:32 Ulrich Müller
2020-05-06  7:49 Ulrich Müller
2020-01-23 13:50 Ulrich Müller
2018-08-27 15:24 Göktürk Yüksek
2015-06-17 12:05 Ulrich Müller
2015-03-14  9:20 Markos Chandras
2013-02-16  0:03 Markos Chandras

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1579931626.b696fdc696574cd1fec19ff572c951c464fe10be.ulm@gentoo \
    --to=ulm@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox