[gentoo-commits] proj/devmanual:master commit in: keywording/

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: Wed,  7 Apr 2021 17:35:28 +0000 (UTC)	[thread overview]
Message-ID: <1617816909.acfc48b80657c6221e1a4000ec046c65cd72fcc6.ulm@gentoo> (raw)

commit:     acfc48b80657c6221e1a4000ec046c65cd72fcc6
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 21 05:18:18 2021 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Apr  7 17:35:09 2021 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=acfc48b8

keywording: call ~arch ("testing") and arch ("stable")

Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 keywording/text.xml | 27 ++++++++++++++-------------
 1 file changed, 14 insertions(+), 13 deletions(-)

diff --git a/keywording/text.xml b/keywording/text.xml
index 6d7c394..0f08c7e 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -38,14 +38,14 @@ The different levels of keyword are:
 
 <dl>
   <dt>
-    <c>arch</c> (<c>x86</c>, <c>ppc-macos</c>)
+    <c>arch</c> (<c>x86</c>, <c>ppc-macos</c>) ("stable")
   </dt>
   <dd>
     Both the package version <e>and</e> the ebuild are widely tested, known to work
     and not have any serious issues on the indicated platform.
   </dd>
   <dt>
-    <c>~arch</c> (<c>~x86</c>, <c>~ppc-macos</c>)
+    <c>~arch</c> (<c>~x86</c>, <c>~ppc-macos</c>) ("testing")
   </dt>
   <dd>
     The package version and the ebuild are believed to work and do not have any
@@ -53,7 +53,7 @@ The different levels of keyword are:
     is considered suitable for <c>arch</c>.
   </dd>
   <dt>
-    No keyword
+    No keyword ("unkeyworded")
   </dt>
   <dd>
     If a package has no keyword for a given arch, it means it is not known
@@ -153,7 +153,7 @@ user system</b>.
 <body>
 
 <important>
-New packages should be marked as <c>~arch</c> only upon
+New packages should be marked as <c>~arch</c> ("testing") only upon
 architectures for which the committing developer has tested.
 </important>
 
@@ -185,7 +185,7 @@ keyworded.
 </p>
 
 <p>
-Do <b>not</b> commit straight to <c>arch</c>.
+Do <b>not</b> commit straight to <c>arch</c> ("stable").
 </p>
 
 </body>
@@ -196,10 +196,10 @@ Do <b>not</b> commit straight to <c>arch</c>.
 <body>
 
 <p>
-When upgrading, drop all existing keywords from <c>arch</c> to <c>~arch</c>, and leave
-any existing <c>~arch</c> keywords intact. This must be done even if you <e>think</e>
-you're just making a trivial fix <d /> there have been several examples of the
-stable tree getting broken this way.
+When upgrading, drop all existing keywords from <c>arch</c> to <c>~arch</c>
+("testing"), and leave any existing <c>~arch</c> keywords intact. This must be
+done even if you <e>think</e> you're just making a trivial fix <d /> there have
+been several examples of the stable tree getting broken this way.
 </p>
 
 <p>
@@ -237,10 +237,11 @@ to do this.
 <body>
 
 <p>
-Stabilization, i.e., moving an ebuild from <c>~arch</c> to <c>arch</c>, is done
-by the relevant architecture teams. If you have access to exotic hardware but
-are not on the arch teams, you may wish to make individual arrangements <d/>
-the arch teams are happy for help, so long as they know what is going on.
+Stabilization, i.e., moving an ebuild from <c>~arch</c> ("testing") to
+<c>arch</c> ("stable"), is done by the relevant architecture teams. If you have
+access to exotic hardware but are not on the arch teams, you may wish to make
+individual arrangements <d/> the arch teams are happy for help, so long as they
+know what is going on.
 </p>
 
 <p>

next             reply	other threads:[~2021-04-07 17:35 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07 17:35 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-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
2015-03-14  9:20 Markos Chandras
2013-02-16  0:03 Markos Chandras

find likely ancestor, descendant, or conflicting patches for this message:
( dfblob:6d7c394 dfblob:0f08c7e )
 OR (
bs:"[gentoo-commits] proj/devmanual:master commit in: keywording/" )
	(help)

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=1617816909.acfc48b80657c6221e1a4000ec046c65cd72fcc6.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