Gentoo Archives: gentoo-commits

From: "Göktürk Yüksek" <gokturk@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] proj/devmanual:master commit in: eclass-writing/
Date: Fri, 30 Aug 2019 15:51:57
Message-Id: 1567180166.56a559843cb4af1c10b1df1b2f3b7c8bfe95bcb5.gokturk@gentoo
1 commit: 56a559843cb4af1c10b1df1b2f3b7c8bfe95bcb5
2 Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
3 AuthorDate: Thu Aug 29 05:54:34 2019 +0000
4 Commit: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
5 CommitDate: Fri Aug 30 15:49:26 2019 +0000
6 URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=56a55984
7
8 eclass-writing: Remove 30-day review requirement
9
10 Remove the requirement of posting API changes for review 30 days prior
11 to committing. It is a dead policy, and we currently perform such
12 changes with regular review periods.
13
14 Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
15
16 eclass-writing/text.xml | 6 ++----
17 1 file changed, 2 insertions(+), 4 deletions(-)
18
19 diff --git a/eclass-writing/text.xml b/eclass-writing/text.xml
20 index 011a3d5..e26dd00 100644
21 --- a/eclass-writing/text.xml
22 +++ b/eclass-writing/text.xml
23 @@ -67,10 +67,8 @@ package, and thus does not typically require changes to be emailed for review.
24 </p>
25
26 <p>
27 -When removing a function or changing the API of an eclass, make
28 -sure that it doesn't break any ebuilds in the tree, and post a
29 -notice to gentoo-dev at least 30 days in advance, preferably with
30 -a patch included.
31 +When removing a function or changing the API of an eclass, make sure that
32 +it doesn't break any ebuilds in the Gentoo repository.
33 </p>
34
35 <p>