From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-commits+bounces-1684493-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits))
	(No client certificate requested)
	by finch.gentoo.org (Postfix) with ESMTPS id 156A0158042
	for <garchives@archives.gentoo.org>; Tue, 29 Oct 2024 17:40:38 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 23F22E082F;
	Tue, 29 Oct 2024 17:40:37 +0000 (UTC)
Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 09405E082F
	for <gentoo-commits@lists.gentoo.org>; Tue, 29 Oct 2024 17:40:37 +0000 (UTC)
Received: from oystercatcher.gentoo.org (oystercatcher.gentoo.org [148.251.78.52])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	by smtp.gentoo.org (Postfix) with ESMTPS id 13A8B34301B
	for <gentoo-commits@lists.gentoo.org>; Tue, 29 Oct 2024 17:40:36 +0000 (UTC)
Received: from localhost.localdomain (localhost [IPv6:::1])
	by oystercatcher.gentoo.org (Postfix) with ESMTP id 547BCB03
	for <gentoo-commits@lists.gentoo.org>; Tue, 29 Oct 2024 17:40:34 +0000 (UTC)
From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Content-Transfer-Encoding: 8bit
Content-type: text/plain; charset=UTF-8
Reply-To: gentoo-dev@lists.gentoo.org, "Ulrich Müller" <ulm@gentoo.org>
Message-ID: <1730219724.f32f4134963c6a157056b68b95503a40d265b0bc.ulm@gentoo>
Subject: [gentoo-commits] proj/devmanual:master commit in: general-concepts/ebuild-revisions/
X-VCS-Repository: proj/devmanual
X-VCS-Files: general-concepts/ebuild-revisions/text.xml
X-VCS-Directories: general-concepts/ebuild-revisions/
X-VCS-Committer: ulm
X-VCS-Committer-Name: Ulrich Müller
X-VCS-Revision: f32f4134963c6a157056b68b95503a40d265b0bc
X-VCS-Branch: master
Date: Tue, 29 Oct 2024 17:40:34 +0000 (UTC)
Precedence: bulk
List-Post: <mailto:gentoo-commits@lists.gentoo.org>
List-Help: <mailto:gentoo-commits+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-commits+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-commits+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-commits.gentoo.org>
X-BeenThere: gentoo-commits@lists.gentoo.org
X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply
X-Archives-Salt: 356c3633-480e-4732-abaa-c5cea9b9abb6
X-Archives-Hash: 92bc42f8f9e8ac86a0c40e99ce07025c

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>