From nobody Mon Apr 29 08:24:39 2024
Delivered-To: importer@patchew.org
Received-SPF: pass (zoho.com: domain of redhat.com designates 209.132.183.37
as permitted sender) client-ip=209.132.183.37;
envelope-from=libvir-list-bounces@redhat.com; helo=mx5-phx2.redhat.com;
Authentication-Results: mx.zoho.com;
spf=pass (zoho.com: domain of redhat.com designates 209.132.183.37 as
permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com;
Return-Path:
Received: from mx5-phx2.redhat.com (mx5-phx2.redhat.com [209.132.183.37]) by
mx.zohomail.com
with SMTPS id 1486113942699447.65602382848897;
Fri, 3 Feb 2017 01:25:42 -0800 (PST)
Received: from lists01.pubmisc.prod.ext.phx2.redhat.com
(lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33])
by mx5-phx2.redhat.com (8.14.4/8.14.4) with ESMTP id v139M9lo054960;
Fri, 3 Feb 2017 04:22:09 -0500
Received: from int-mx13.intmail.prod.int.phx2.redhat.com
(int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26])
by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP
id v139M80f002597 for ;
Fri, 3 Feb 2017 04:22:08 -0500
Received: from inaba.usersys.redhat.com ([10.34.129.229])
by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP
id v139M6E8010410
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256
verify=NO); Fri, 3 Feb 2017 04:22:07 -0500
From: Andrea Bolognani
To: libvir-list@redhat.com
Date: Fri, 3 Feb 2017 10:22:03 +0100
Message-Id: <1486113723-22086-1-git-send-email-abologna@redhat.com>
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.26
X-loop: libvir-list@redhat.com
Cc: pkrempa@redhat.com
Subject: [libvirt] [PATCH] docs: Release notes should be updated in a
separate commit
X-BeenThere: libvir-list@redhat.com
X-Mailman-Version: 2.1.12
Precedence: junk
List-Id: Development discussions about the libvirt library & tools
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Sender: libvir-list-bounces@redhat.com
Errors-To: libvir-list-bounces@redhat.com
X-ZohoMail: RSF_0 Z_629925259 SPT_0
Content-Type: text/plain; charset="utf-8"
Updating docs/news.xml in the same commit that performs the
documented change makes backports needlessly complicated,
both for mainteinance branches and downstream distributions,
because it introduces additional potential for merge
conflicts.
Document in the contributor guidelines that the release notes
should be updated in a separate commit instead, so that it's
easy to backport just the code change.
---
docs/hacking.html.in | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/docs/hacking.html.in b/docs/hacking.html.in
index c7bbcbd..b1bb149 100644
--- a/docs/hacking.html.in
+++ b/docs/hacking.html.in
@@ -302,7 +302,8 @@
or fixing all but the most obscure bugs, must be (briefly) describ=
ed
in a release notes entry; changes that are only relevant to other
libvirt developers, such as code refactoring, don't belong in the
- release notes.
+ release notes. Note that docs/news.xml
should be upda=
ted
+ in its own commit not to get in the way of backports.
=20
--=20
2.7.4
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list