Re: gdb-7.11.1 re-spin update

Simon Marchi
2016-05-03T14:19:40Z

On 16-04-25 05:49 PM, Joel Brobecker wrote:
> I notice that the "Done" list has some items explicitly listed,
> and then a generic item giving a link to bugzilla for all bugs
> identified for 7.11.1, or else fixed for 7.11.1.
>
> I could conceive of using this kind of generic link for bugs
> identified as critical for 7.11, provided that we make sure that
> these bugs are always assigned to someone. Otherwise, we cannot
> know who to contact for an update when we get closer to the release.
> That being said, I have some reservations about this, because
> it is harder to make sure that whoever sets the target milestones
> does so after having consulted the group about it. Personally,
> I would prefer that we explicitly list each item in the wiki's
> TODO, because anyone can subscribe to updates here, and make sure
> that these updates were agreed upon before being added.
>
> For the "Done" section, on the other hand, using the generic
> link is a bit of a regression for me. Now, instead of copy/pasting
> one list (into the news webpage, and then the announcement email),
> I now have to copy/paste one list, then go to bugzilla and then
> massage another list into looking like the first one, so I can append
> that list too.

I think that this particular problem could be efficiently solved with scripting.
Apparently, Bugzilla now has an API [1], although I can't find how to use it on
the sourceware BZ, maybe it's too old.

If that API was accessible, it should be easy to write a script that prints a
nicely formatted list of all issues with target milestone == 7.11.1, ready to
copy paste in the email. It could also tell which issues are still open and warn
if any of these doesn't have an assignee. So it could give you a quick overview
of the state of the release.

If we could get the BZ API working, I am sure we would find many other uses.

Simon

[1] https://bugzilla.readthedocs.io/en/5.0/api/core/v1/general.html