]> git.ipfire.org Git - thirdparty/libvirt.git/commit
docs: Release notes should be updated in a separate commit
authorAndrea Bolognani <abologna@redhat.com>
Fri, 3 Feb 2017 09:19:12 +0000 (10:19 +0100)
committerAndrea Bolognani <abologna@redhat.com>
Fri, 3 Feb 2017 09:49:15 +0000 (10:49 +0100)
commit54eaf639a5e94cda1f705cf43e196aec0262aa7c
tree498b7f8f5af96abb2f2cde16df15cc7d8292e622
parentf86a7a837207a1260ff7a8e4469b9057fbde11c8
docs: Release notes should be updated in a separate commit

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