Re: Anyone who could share their Perl knowledge (to make Bugzilla display a product overview page when new bug entry is disabled)?
On Wed, 2019-02-27 at 16:35 +0100, Bastien Nocera wrote: > On Wed, 2019-02-27 at 14:34 +0100, Andre Klapper wrote: > > 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=%E2%9C%93=opened_username=hadess=migrate > > (the majority of them I only just opened, the first 3 are getting old > though) Probably requires csoriano et al to find time. (Cannot answer myself as I'm not involved in running or maintaining the migration script.) > > 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. Good catch, thanks. That should be fixed by https://gitlab.gnome.org/Infrastructure/bugzilla-gnome-org-customizations/commit/75366086f03c3675b7ad93af6ec1cb3910b38d10 once that change gets deployed on the production server. > It seems that the bugzilla migration script might not know how to > migrate private, or security bugs. https://gitlab.gnome.org/World/bztogl/issues/33 > What about the rest of the security bugs? I found left-over security > bugs in gdk-pixbuf and gvfs for example. I also need to defer that question to csoriano et al... andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Anyone who could share their Perl knowledge (to make Bugzilla display a product overview page when new bug entry is disabled)?
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=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=%E2%9C%93=opened_username=hadess=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
Re: Anyone who could share their Perl knowledge (to make Bugzilla display a product overview page when new bug entry is disabled)?
El mié., 27 feb. 2019 15:10, Daniel Mustieles García < daniel.mustie...@gmail.com> escribió: > Hi Andre, > > I think Gtranslator's old bugs could be simply deleted or closed, since > the new version fixes most of them, and the other ones are deprecated. > > Ccing Daniel García, so he can give us his opinion about this. > Yes, old bug can be deleted. > Thanks! > > El mié., 27 feb. 2019 a las 14:35, Andre Klapper () > escribió: > >> 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=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. >> We still have 22015 open tickets in 190 Bugzilla products... >> >> Happy cleanup! >> andre >> -- >> Andre Klapper | ak...@gmx.net >> https://blogs.gnome.org/aklapper/ >> >> >> ___ >> desktop-devel-list mailing list >> desktop-devel-list@gnome.org >> https://mail.gnome.org/mailman/listinfo/desktop-devel-list >> > ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Anyone who could share their Perl knowledge (to make Bugzilla display a product overview page when new bug entry is disabled)?
Hi Andre, I think Gtranslator's old bugs could be simply deleted or closed, since the new version fixes most of them, and the other ones are deprecated. Ccing Daniel García, so he can give us his opinion about this. Thanks! El mié., 27 feb. 2019 a las 14:35, Andre Klapper () escribió: > 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=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. > We still have 22015 open tickets in 190 Bugzilla products... > > Happy cleanup! > andre > -- > Andre Klapper | ak...@gmx.net > https://blogs.gnome.org/aklapper/ > > > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list > ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Anyone who could share their Perl knowledge (to make Bugzilla display a product overview page when new bug entry is disabled)?
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=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. We still have 22015 open tickets in 190 Bugzilla products... Happy cleanup! andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Anyone who could share their Perl knowledge (to make Bugzilla display a product overview page when new bug entry is disabled)?
Currently GNOME Bugzilla does not show the "Browse" product page when a product has been disabled for new bug entry (that's the case for nearly all Bugzilla products now, as we make progress migrating to Gitlab). Which is annoying for maintainers who want to clean up a bit. https://bugzilla.gnome.org/show_bug.cgi?id=796811 links to the corresponding custom code line. Help welcome to fix that properly (I don't understand Perl enough but am happy to test patches locally). Thanks, andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
