[gentoo-commits] proj/devmanual:master commit in: general-concepts/ebuild-revisions/

["Ulrich Müller" <ulm@gentoo.org>]

commit:     f32f4134963c6a157056b68b95503a40d265b0bc
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Oct 14 00:01:45 2024 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Tue Oct 29 16:35:24 2024 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=f32f4134

general-concepts/ebuild-revisions: mention balancing examples against stable

Explicitly say that even 'no revision bump' examples should be balanced
against whether a stable ebuild is being modified, as we want to minimize
any risk of regressions there.

i.e. It might be that a change would not need a revbump for an ~arch-only
ebuild, but if the ebuild is stable, the principle of being conservative
ofr stable would mean a revbump is warranted.

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

 general-concepts/ebuild-revisions/text.xml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/general-concepts/ebuild-revisions/text.xml b/general-concepts/ebuild-revisions/text.xml
index 2c8531a..72087f0 100644
--- a/general-concepts/ebuild-revisions/text.xml
+++ b/general-concepts/ebuild-revisions/text.xml
@@ -125,6 +125,11 @@ of thumb could be used as a guideline:
   </li>
 </ul>
 
+<p>
+Note that the examples above should still be balanced against the general
+principle of conservatism and need to minimize risk for stable users.
+</p>
+
 </body>
 </chapter>
 </guide>