commit: 9f63cc9e468400cc0feb64c3bd45cedb525b0451 Author: Michał Górny <mgorny <AT> gentoo <DOT> org> AuthorDate: Fri Sep 6 05:57:23 2019 +0000 Commit: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org> CommitDate: Fri Sep 20 22:51:10 2019 +0000 URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=9f63cc9e
eclass-writing: Make even more explicit, per gentoo-dev Change 'should' into 'must' for initial reviews. Make it clear that per-package eclass exception applies only to updates. ML-Thread: https://archives.gentoo.org/gentoo-dev/message/122108eebce1c4da00a1838896b4b1c3 Signed-off-by: Michał Górny <mgorny <AT> gentoo.org> Signed-off-by: Göktürk Yüksek <gokturk <AT> gentoo.org> eclass-writing/text.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/eclass-writing/text.xml b/eclass-writing/text.xml index e26dd00..1bc1768 100644 --- a/eclass-writing/text.xml +++ b/eclass-writing/text.xml @@ -46,9 +46,9 @@ Roughly speaking, there are three kinds of eclass: <body> <p> -Before committing a new eclass to the tree, it should be emailed to the -gentoo-dev mailing list with a justification and a proposed implementation. Do -not skip this step <d/> sometimes a better implementation or an alternative which +Before committing a new eclass to the tree, it must be emailed to the gentoo-dev +mailing list with a justification and a proposed implementation. Do not skip +this step <d/> sometimes a better implementation or an alternative which does not require a new eclass will be suggested. </p> @@ -61,7 +61,7 @@ and end up breaking something, expect to be in a lot of trouble. </p> <p> -The exceptions to this rule are per-package eclasses. For example, +The exceptions to this rule are updates to per-package eclasses. For example, the <c>apache-2</c> eclass is only used by the <c>www-servers/apache</c> package, and thus does not typically require changes to be emailed for review. </p>
