GNOME Bugzilla – Bug 584590
Separate gnomemm products
Last modified: 2011-01-16 23:31:42 UTC
C++ language binding modules such as gconfmm, goocanvamm, gstreamermmm, etc, are currently just components in a gnomemm bugzilla product. We would like to make them separate products in bugzilla. Luckily, there are not many bugs filed against gnomemm. Here are the product descriptions: cluttermm: C++ bindings for clutter. clutter-box2dmm: C++ bindings for clutter-box2d. clutter-gtkmm: C++ bindings for clutter-gtk. clutter-gstreamermm: C++ bindings for clutter-gstreamer cluttermm_tutorial: A tutorial for cluttermm. libglademm: C++ bindings for libglade. libgnomemm: : C++ bindings for libgnome. libgdamm: : C++ bindings for libgda. libgnomedbmm: C++ bindings for libgnomedb. libgnomecanvasmm: C++ bindings for libgnomecanvas libgnomeuimm: C++ bindings for libgnomeui. libpanelappletmm: C++ bindings for libpanelapplet. gconfmm: C++ bindings for GConf. goocanvasmm: C++ bindings for goocanvas. gnome-vfsmm: C++ bindings for gnome-vfm. gstreamermm: C++ bindings for gstreamer. geglmm: C++ bindings for geglmm. gstreamermm-plugins-good: C++ bindings for gstreamer-plugins-good The default assignee (and QA contact) should be: gtkmm-forge@lists.sourceforge.net though I guess it would be nice to have a bugzilla alias to use instead.
For geglmm I would appreciate an alias for the product that is not gtkmm's.
Hi Murray are those bindings rather quite individual and independent to justify one bugzilla product for each? I always thought they are closely related. Well, to be honest it will take me at least 1 hour or so to set up that many products. But if you really benefit I will do so.
They are as dependent to each other as the original C libraries are. It use to be that they were all in the same svn module, but this is no longer the case in git.
(In reply to comment #2) > Hi Murray > > are those bindings rather quite individual and independent to justify one > bugzilla product for each? It's as justified for bugzilla as it is for git. We used to try to make life easier for other people by hiding our stuff under gnomemm in cvs/svn/git, but it was recently decided that we should split them out to avoid confusion. And it's always been a problem for people to know where to file bugs for, e.g., goocanvasmm. They don't know to look in gnomemmm. So, yes, please, we really do need this. Thanks for your time.
A large pile of products was created. (Only) you can maintain them here http://bugzilla.gnome.org/editproducts.cgi?action=edit&product=cluttermm http://bugzilla.gnome.org/editproducts.cgi?action=edit&product=clutter-box2dmm http://bugzilla.gnome.org/editproducts.cgi?action=edit&product=clutter-gtkmm http://bugzilla.gnome.org/editproducts.cgi?action=edit&product=clutter-gstreamermm http://bugzilla.gnome.org/editproducts.cgi?action=edit&product=cluttermm_tutorial http://bugzilla.gnome.org/editproducts.cgi?action=edit&product=libglademm http://bugzilla.gnome.org/editproducts.cgi?action=edit&product=libgnomemm http://bugzilla.gnome.org/editproducts.cgi?action=edit&product=libgdamm http://bugzilla.gnome.org/editproducts.cgi?action=edit&product=libgnomedbmm http://bugzilla.gnome.org/editproducts.cgi?action=edit&product=libgnomecanvasmm http://bugzilla.gnome.org/editproducts.cgi?action=edit&product=libgnomeuimm http://bugzilla.gnome.org/editproducts.cgi?action=edit&product=libpanelappletmm http://bugzilla.gnome.org/editproducts.cgi?action=edit&product=gconfmm http://bugzilla.gnome.org/editproducts.cgi?action=edit&product=goocanvasmm http://bugzilla.gnome.org/editproducts.cgi?action=edit&product=gnome-vfsmm http://bugzilla.gnome.org/editproducts.cgi?action=edit&product=gstreamermm http://bugzilla.gnome.org/editproducts.cgi?action=edit&product=geglmm http://bugzilla.gnome.org/editproducts.cgi?action=edit&product=gstreamermm-plugins-good You need to add at least one component each before new bugs can be filed. Use cluttermm-maint@gnome.bugs clutter-box2dmm-maint@gnome.bugs clutter-gtkmm-maint@gnome.bugs clutter-gstreamermm-maint@gnome.bugs cluttermm_tutorial-maint@gnome.bugs libglademm-maint@gnome.bugs libgnomemm-maint@gnome.bugs libgdamm-maint@gnome.bugs libgnomedbmm-maint@gnome.bugs libgnomecanvasmm-maint@gnome.bugs libgnomeuimm-maint@gnome.bugs libpanelappletmm-maint@gnome.bugs gconfmm-maint@gnome.bugs goocanvasmm-maint@gnome.bugs gnome-vfsmm-maint@gnome.bugs gstreamermm-maint@gnome.bugs geglmm-maint@gnome.bugs gstreamermm-plugins-good-maint@gnome.bugs as QA contact and default assignee for new components. Make anyone (including you) interested in following all activity watch above dummy email addresses. Do so by adding them to the 'users to watch' list under Account->Email preferences.
Can I be made owner for geglmm ? I can't create components if I'm not.
Done. Now please talk to Murray for all maintenance on those modules.
Thanks Christian. But we still need a product for gtksourceviewmm: http://bugzilla.gnome.org/buglist.cgi?product=gnomemm&bug_status=NEW&bug_status=REOPENED&bug_status=ASSIGNED&bug_status=UNCONFIRMED For the other products: I've added "general" components to each of them, with the appropriate QA contact and default assignee. Hopefully I have not made any mistakes. They will get version numbers next time we use install-module to release a tarball. I have reassigned all gnomemm bugs apart from the gtksourceviewmm which still needs a product. I made Jonathan Jongsma and Daniel Elstner "developers" for these products too (apart from geglmm), so things don't need to block on me. We need to figure out how to get bugmail for these sent to our gtkmm-forge mailing list (whose digests are sent to gtkmm-list so that more people see them).
Product gtksourceviewmm created. (Only) you can maintain it here http://bugzilla.gnome.org/editproducts.cgi?action=edit&product=gtksourceviewmm You need to add at least one component before new bugs can be filed. Use gtksourceviewmm-maint@gnome.bugs as QA contact and default assignee for new components. Make anyone (including you) interested in following all activity watch above dummy email address. Do so by adding it to the 'users to watch' list under Account->Email preferences.
OLAV, what would be a clever way to send all bug activity to a mailing list? create a fake user with the list's address and watch a product?
We already do this with glibmm and gtkmm, via the gtkmm-forge user/alias. I don't know if it's a user or an alias though. By the way, that gtkmm-forge mailing list then sends a _digest_ to the real mailing list. I wish that bugzilla could just directly send a digest of recent activity to a mailing list.
(In reply to comment #9) > Product gtksourceviewmm created. > > (Only) you can maintain it here > > http://bugzilla.gnome.org/editproducts.cgi?action=edit&product=gtksourceviewmm > > You need to add at least one component before new bugs can be filed. > Use > > gtksourceviewmm-maint@gnome.bugs > > as QA contact and default assignee for new components. > Make anyone (including you) interested in following all activity > watch above dummy email address. Do so by adding it to the > 'users to watch' list under Account->Email preferences. Done. Thanks.
Can this report be closed then?
Yes. Thanks. Note that I'd still like a way to send an email digest to our mailing list, but that's a separate issue.
Actually, could you please remove the old gnomemm product now, to avoid confusion.
I closed that product for new bug entry. Please mind the bugs: https://bugzilla.gnome.org/buglist.cgi?product=gnomemm Can they be moved?
Thanks. Yes, they could be moved to the product with the same name as their current components. But there are 270 of them and I'd prefer not to do that by manually.
(There are no open bugs in the gnomemm product.)