This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: gdb-7.11.1 re-spin update
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 2 May 2016 08:46:42 -0700
- Subject: Re: gdb-7.11.1 re-spin update
- Authentication-results: sourceware.org; auth=none
- References: <20160425214951 dot GA4079 at adacore dot com> <571F5BF8 dot 4090205 at redhat dot com>
Hi Pedro,
Sorry I wasn't able to anwer this any sooner...
> I was the one who first added these urls, sorry if it causes
> you trouble, and sorry that I didn't reach out to you before
> actually doing it. I thought in good faith that that would
> be an obvious improvement.
>
> Let me explain what went through my mind:
It makes sense.
On the other hand, the first advantage of having it in the wiki was
that I was able to subscribe to the release wiki page, and therefore
get an email each time a chnage in made. The side effect of that I can
then double-check the entries added, and in particular checking that
someone is assigned that entry.
If there is a way for me to subscribe to all bugzilla PRs that get
assigned a specific release version, then the downside of using
bugzilla only is less. I might still have to open the bugzilla PR
to verify that the PR is assigned to someone, but given the number
of such PRs, I can live with that. But the question is - can we
subscribe to a category or all of bugzilla?
Otherwise, if someone is already tracking bugzilla PRs and also
understands the release process, I am fine delegating this part
of the work. One of the important aspects of that is making sure
that the information remains accurate, at least up to release;
so that the release announcement is as correct as can be.
WDYT?
--
Joel