gtkmm-3.bst and other *mm*.bst files out of date
A number of .bst files for "mm" modules with C++ bindings need updating. Can I do that myself? Shall I open an MR? Is this issue enough? I don't know the rules for gnome-build-meta. In jhbuild, I push commits to the .modules files myself without asking a jhbuild maintainer, when something shall be changed for modules that I work with. Can I do that with .bst files in gnome-build-meta as well?
What I have found, assuming that the intention is to build the latest versions:
core-deps/atkmm-1.6.bst
track: atkmm-2-24
shall be
track: atkmm-2-28
core-deps/glibmm-2.4.bst
track: glibmm-2-54
shall be
track: glibmm-2-60
core-deps/gtkmm-3.bst
track: gtkmm-3-22
shall be
track: gtkmm-3-24
core-deps/pangomm-1.4.bst
track: pangomm-2-40
shall be
track: pangomm-2-42
There are no world/gtkmm-documentation.bst and world/gtkmm-3-documentation.bst, analogous to the corresponding entries in jhbuild/modulesets/gnome-world.modules. Is that a deliberate omission?
In the near future mm-common can be built with meson instead of autotools, I hope. That will affect core-deps/mm-common.bst.