public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: keywording/
Date: Wed, 16 Mar 2022 14:52:03 +0000 (UTC)	[thread overview]
Message-ID: <1647442310.a4d5e702ddea5f01980e667d6673decdcc8a68e9.sam@gentoo> (raw)

commit:     a4d5e702ddea5f01980e667d6673decdcc8a68e9
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Mar  1 09:49:54 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Mar 16 14:51:50 2022 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=a4d5e702

keywording: describe pending stabilization requests

Describe how maintainers should keep track of (and know when to file)
pending stabilization requests.

Signed-off-by: Sam James <sam <AT> gentoo.org>

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

diff --git a/keywording/text.xml b/keywording/text.xml
index 74224a0..c5b5660 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -429,6 +429,36 @@ stable for one of these architectures.
 </body>
 </subsection>
 
+<subsection>
+<title>Keeping track of pending stabilizations</title>
+<body>
+
+<p>
+Maintainers need some method or system to organize and start pending
+stabilizations once they become due.
+</p>
+
+<p>
+There are several tools available that can help with this:
+</p>
+
+<ul>
+  <li>
+    Use <c>imlate</c> from app-portage/gentoolkit
+  </li>
+  <li>
+    Use packages.gentoo.org's maintainer pages (which have a Stabilization
+    tab)
+  </li>
+  <li>
+    Use <c>pkgcheck</c>'s <c>StableRequest</c> check, e.g.
+      <c>grep -ri "larry@" */*/metadata.xml -l | cut -d'/' -f1-2 | xargs pkgcheck scan -k StableRequest</c>
+  </li>
+</ul>
+
+</body>
+</subsection>
+
 <subsection>
 <title>Simultaneous stabilization on all architectures</title>
 <body>


             reply	other threads:[~2022-03-16 14:52 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 14:52 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-14 17:07 [gentoo-commits] proj/devmanual:master commit in: keywording/ 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
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=1647442310.a4d5e702ddea5f01980e667d6673decdcc8a68e9.sam@gentoo \
    --to=sam@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