The uniqueness of bugs on gitlab.gnome.org is defined by the bug number, the project's name but also the user's name: GNOME must be part of the bug definition. It's very similar to GitHub here: https://en.opensuse.org/openSUSE:Packaging_Patches_guidelines#Current_set_of_abbreviations.
Without that, you wuldn't't be able to identify bugs for https://gitlab.gnome.org/danigm/fractal or https://gitlab.gnome.org/aplazas/libmanette. So either you want the parsers to interpret two formats for bgo# (may be problematic for retro compatibility) or you want to create a new one. The format could be somthing like: glgo#GNOME/gnome-shell-extensions#10. Cheers, Adrien Plazas >>> Yifan Jiang <[email protected]> 11/28/17 10:41 AM >>> Dear hackers, It seems GNOME is moving steadily to migrate bgo bugs to gitlab, and finally gitlab will probably replace bgo: https://mail.gnome.org/archives/desktop-devel-list/2017-May/msg00051.html Shall we have something replacing bgo# abbreviation in literal part of packages (changelog, spec etc.)? The hard part might be the gitlab issue number seems not unique, e.g. when xiaoguang was handling the bgo#745064, he found the issue was moved to: https://gitlab.gnome.org/GNOME/gnome-shell-extensions/issues/10 whose uniqueness is defined by the "name of component" and "the number of the issue". It is fine by now since we still have a bgo# number to track. When the issues reported only on the gitlab, we might want to have some extra tag to mark them. Do you have some thoughts on this? Thanks! - Yifan -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
