This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: RFC: documenting all gdb-7.6 branch patches
- From: Pedro Alves <palves at redhat dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 08 May 2013 18:34:07 +0100
- Subject: Re: RFC: documenting all gdb-7.6 branch patches
- References: <20130508052420 dot GR5278 at adacore dot com>
On 05/08/2013 06:24 AM, Joel Brobecker wrote:
> as briefly discussed a few months ago, I would like all patches
> that are applied to the branch to be documented somewhere. The
> purpose of this document would be for me to have something I can
> simply copy/paste when I announce the minor/corrective release.
> So far, I have been going through each and every patch, trying
> to figure out what the intent was, but this is very time consuming
> and not always accurate.
>
> My proposal of using the NEWS file had a rather tepid reaction,
> so I am proposing instead that we use the GDB 7.6 release wiki page.
> I can add a section at the top of the page listing the changes applied
> since the GDB 7.6 release, and explaining their effect and why they
> matter to the user.
I agree. The wiki is a good place for this.
> Additionally, I'd like the description to be reviewed on gdb-patches
> before the patch is ported to the branch, and the description is added
> to the list.
That's fine with me.
> Would that be a workable approach?
I think so.
For bug fixes, it'll probably be good to make sure there's always a
PR in bugzilla to point at, even if we still give a short description
of the bug in the release notes in addition to the PR number / link.
--
Pedro Alves