From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/
Date: Sun, 22 May 2016 08:35:59 +0000 (UTC) [thread overview]
Message-ID: <1463906141.158d182b0142a90aae7b6c860c923659c78b3f97.ulm@gentoo> (raw)
commit: 158d182b0142a90aae7b6c860c923659c78b3f97
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Wed May 18 12:07:32 2016 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Sun May 22 08:35:41 2016 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=158d182b
ebuild-maintenance: Add news items to agenda for package moves.
This policy is already outlined in GLEP 42.
Bug: 583404
ebuild-maintenance/text.xml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/ebuild-maintenance/text.xml b/ebuild-maintenance/text.xml
index a2fe6b8..3e30933 100644
--- a/ebuild-maintenance/text.xml
+++ b/ebuild-maintenance/text.xml
@@ -482,6 +482,11 @@ Here is an example where the package
<li>
Commit all the changes in one commit using: <c>git commit --gpg-sign</c>
</li>
+ <li>
+ Update any <uri link="::general-concepts/news">news items</uri>
+ referencing the package in a <c>Display-If-Installed</c> header
+ or in the item's body (and increment their <c>Revision</c>).
+ </li>
<li>Update any open bugs related to the package</li>
</ol>
next reply other threads:[~2016-05-22 8:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-22 8:35 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-23 8:40 [gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/ Ulrich Müller
2017-09-25 4:40 Göktürk Yüksek
2017-09-25 4:40 Göktürk Yüksek
2017-07-29 20:48 Göktürk Yüksek
2017-01-22 20:45 Göktürk Yüksek
2016-11-20 20:46 Göktürk Yüksek
2016-08-18 9:01 Ulrich Müller
2016-05-01 3:49 Göktürk Yüksek
2016-04-24 0:47 Göktürk Yüksek
2016-04-23 19:26 Göktürk Yüksek
2016-04-19 10:40 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2015-05-09 15:22 Ulrich Müller
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=1463906141.158d182b0142a90aae7b6c860c923659c78b3f97.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