提交 54eaf639 编写于 作者: A Andrea Bolognani

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.
上级 f86a7a83
...@@ -302,7 +302,8 @@ ...@@ -302,7 +302,8 @@
or fixing all but the most obscure bugs, must be (briefly) described or fixing all but the most obscure bugs, must be (briefly) described
in a release notes entry; changes that are only relevant to other in a release notes entry; changes that are only relevant to other
libvirt developers, such as code refactoring, don't belong in the libvirt developers, such as code refactoring, don't belong in the
release notes.</p> release notes. Note that <code>docs/news.xml</code> should be updated
in its own commit not to get in the way of backports.</p>
</li> </li>
</ol> </ol>
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册