This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Update on commit and release workflow discussions
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Siddhesh Poyarekar <siddhesh at redhat dot com>
- Cc: <libc-alpha at sourceware dot org>, <carlos at redhat dot com>, <roland at hack dot frob dot com>
- Date: Mon, 17 Aug 2015 17:24:40 +0000
- Subject: Re: Update on commit and release workflow discussions
- Authentication-results: sourceware.org; auth=none
- References: <20150817115747 dot GC2415 at spoyarek dot pnq dot redhat dot com> <alpine dot DEB dot 2 dot 10 dot 1508171441030 dot 29836 at digraph dot polyomino dot org dot uk> <20150817171102 dot GD2415 at spoyarek dot pnq dot redhat dot com>
On Mon, 17 Aug 2015, Siddhesh Poyarekar wrote:
> OK, so 'Resolves:' to indicate that a bug has been fixed and the bz can
> be closed? Then we don't have to depend on the ChangeLog [BZ #] at all.
Yes, that would do the job. You still need a way to avoid a bug getting
in the list of fixed bugs if the bug number in the Resolves line was wrong
(this includes it being a bug that was fixed long ago, as well as a bug
that the Resolves line caused to be wrongly closed and was then reopened),
or if the fix had to be reverted or turned out to be incomplete (without
the bug getting fully fixed again before the release), and a way to get a
bug in that list if someone omitted the Resolves line when committing the
fix (or only realized later that there was a bug open for the issue).
--
Joseph S. Myers
joseph@codesourcery.com