public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Markos Chandras" <hwoarang@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: keywording/
Date: Sat, 14 Mar 2015 09:20:52 +0000 (UTC)	[thread overview]
Message-ID: <1426324726.9c2e6f500a276b974bc2e2bd476d8423f113dbb2.hwoarang@gentoo> (raw)

commit:     9c2e6f500a276b974bc2e2bd476d8423f113dbb2
Author:     Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Thu Mar 12 13:29:40 2015 +0000
Commit:     Markos Chandras <hwoarang <AT> gentoo <DOT> org>
CommitDate: Sat Mar 14 09:18:46 2015 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=9c2e6f50

Document the new ALLARCHES process.

Per the latest council meeting, it is now possible to request a
stabilization on all arches at once (for architecture-independent
packages). This commit documents the new keyword and process on the
"Keywording" page.

Link: http://archives.gentoo.org/gentoo-dev/message/5d96b51ced1d1ed126951f117c828482
X-Gentoo-Bug: 543062
X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=543062

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

diff --git a/keywording/text.xml b/keywording/text.xml
index e22a76a..c386427 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -268,6 +268,32 @@ Vulnerability Treatment Policy</uri>
 </body>
 </section>
 
+<subsection>
+  <title>
+    Simultaneous stabilization on all architectures
+  </title>
+  <body>
+    <p>
+      If you maintain an architecture-independent package (data files,
+      icons, pure Perl,...) then you may request that your
+      package be stabilized on all arches at once. To do this<d />when
+      you are filing the stabilization bug<d />please add the keyword
+      <c>ALLARCHES</c> in addition to <c>STABLEREQ</c> and CC the
+      arches that you would like to stabilize.
+    </p>
+
+    <p>
+      The arch teams, when encountering the <c>ALLARCHES</c> keyword,
+      should perform their usual set of tests on a single convenient
+      architecture. Then, if everything works, stabilize not only the
+      arch that was used during testing, but also all of the other
+      arches in CC on the bug. Afterwards, the CC field can be cleared
+      and the bug closed if appropriate.
+    </p>
+  </body>
+</subsection>
+
+
 <section>
 <title>Removing Package Versions</title>
 <body>


             reply	other threads:[~2015-03-14  9:20 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-14  9:20 Markos Chandras [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-07-30  7:59 [gentoo-commits] proj/devmanual:master commit in: keywording/ Ulrich Müller
2025-07-30  7:59 Ulrich Müller
2025-07-30  7:59 Ulrich Müller
2022-03-16 14:52 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-25  6:02 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
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=1426324726.9c2e6f500a276b974bc2e2bd476d8423f113dbb2.hwoarang@gentoo \
    --to=hwoarang@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