On Wed, 2019-02-27 at 14:34 +0100, Andre Klapper wrote: > On Tue, 2019-02-26 at 08:19 +0100, Andre Klapper wrote: > > Currently GNOME Bugzilla does not show the "Browse" product page > > when a > > product has been disabled for new bug entry > > Fixed now thanks to the help of Carlos and Olav. Pages like > https://bugzilla.gnome.org/page.cgi?id=browse.html&product=gnome-shell > work again so you can see all your old boogs and triage them! Right? > > If you want your project's (open) Bugzilla tasks to get copied to > Gitlab one day in the future: A ticket at > https://gitlab.gnome.org/Infrastructure/GitLab/issues/ > is welcome to sort out things.
Is there a timeline for migration? I've filed a few of those, and haven't had any feedback: https://gitlab.gnome.org/Infrastructure/GitLab/issues/?scope=all&utf8=%E2%9C%93&state=opened&author_username=hadess&search=migrate (the majority of them I only just opened, the first 3 are getting old though) > We still have 22015 open tickets in 190 Bugzilla products... It would have been easier if closing the products for new bugs didn't remove those products from the "watched products" section in the drop- down, probably on purpose. Instead, you'll need to go to the email preferences: https://bugzilla.gnome.org/userprefs.cgi?tab=email and enter the watched products one by one. It seems that the bugzilla migration script might not know how to migrate private, or security bugs. This evince bug for example, is still opened because the reporter ticked the "only Evince developers can see this": https://bugzilla.gnome.org/show_bug.cgi?id=784704 What about the rest of the security bugs? I found left-over security bugs in gdk-pixbuf and gvfs for example. Cheers _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
