Re: gdb-7.11.1 re-spin update

Pedro Alves
2016-05-02T17:23:53Z

On 05/02/2016 04:46 PM, Joel Brobecker wrote:

> 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?

Bugzilla supports sending notifications when the milestone changes,
(it's in the preferences page), but I don't how to do that when
you're not the assignee/reporterd/cced to the bug.

What I do, is subscribe to the gdb-prs mailing list:

https://sourceware.org/ml/gdb-prs/

so I get a message for _every_ change done on our bugzilla.

I follow this list like I follow gdb-patches@. I have a mail
filter that puts all gdb-prs traffic on its own mail/imap dir.

(Note one can reply to these bugzilla email via email too, which
is convenient at times.)

For example, I just now changed the milestone of PR build/20029
to 7.11.1, and that generated this mail:

https://sourceware.org/ml/gdb-prs/2016-q2/msg00171.html

( and just using the bugzilla interface for that was quite
convenient. :-) )

Guess if one wanted, one could easily set up a mail filter
based on "List-id: gdb-prs" and the "Target Milestone" string
being present in the mail body.

> Otherwise, if someone is already tracking bugzilla PRs and also
> understands the release process, I am fine delegating this part
> of the work.

At least I track bugzilla PRs. I had assumed all maintainers did.
I don't reply to all PRs, there's just not enough time
unfortunately, but at least I read all and have been trying to
make sure milestones are set.

> 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.

Given that the entries in the wiki page are just the
PR title, I think that ends up being the same amount or even
less work. If a bug has an incomplete or inaccurate title,
we should just fix it on the bug directly, IMO.

Thanks,
Pedro Alves