GNOME Bugzilla – Bug 627963
Add a way to get notifications for glib/introspection bugs
Last modified: 2018-08-21 08:25:54 UTC
I'd like to be able to get an email as soon as a glib/introspection bug changes, without actually subscribing to _all_ bugs in the glib component. Andre has told me that the best way is to add a new alias and change the default QA assign, but it means that all existing bugs would have to be updated to point to that field. That might best be done directly against the bug database so mass-emailing can be avoided.
I proposed to change the Default QA Contact for glib/introspection to a new alias like glib-introspection-maint@gnome.bugs Changing for all existing tickets means triggering bugmail for 595 reports. <andre> jdahlin: so can you please file a bug report, and ask the gtk/glib crew first to not kill me for mass-mailbombing them when I'd do that?
Andre: do you have direct database access, manipulating SQL directly a viable option for updating existing bugs? I'm one of the maintainer of gobject-introspection and for me it would be fine to do some spamming, if there's no other reasonable way to do the same. Basically, just something like this: UPDATE bugs WHERE component_id = X SET qa_contact = Y; It would just involve finding out the ids for the component and the qa contact.
(In reply to comment #2) > Andre: do you have direct database access Nope.
Such a SQL statement is not enough; it also has to change the history.
https://bugzilla.gnome.org/describecomponents.cgi?product=glib Currently gtkdev@gtk.org is the assignee. Is that a real email address? @Johan: If implementing this, should gtkdev@gtk.org also watch glib-introspection-maint@gnome.bugs ? If not, should people be explicitly notified of the fact that they have to add glib-introspection-maint@gnome.bugs to their watchlist under https://bugzilla.gnome.org/userprefs.cgi?tab=email to still receive introspection component bugmail? Has this been discussed / agreed on in the gtk+ community (e.g. monthly team meetings)?
NEEDINFO as per comment 5. Related but about GTK: https://mail.gnome.org/archives/gtk-devel-list/2012-August/msg00063.html
Migrating to Gitlab hence closing as wontfix