Re: git commit->bugzilla for glibc

[Roland McGrath <roland at hack dot frob dot com>]

> This is the first I've read about this.  If you'd like to install
> a git log-parsing hook on the server, I can probably help.

I thought you might!  The glibc admin bug says that the first step is to
talk to you. :-)  But nobody on our end followed up even as far as that.
I can't recall if I just failed to get around to pinging you myself, or
if I explicitly decided that someone else interested in glibc project
infrastructure ought to drive the subject just as a needed test case for
the community actually doing anything to improve its infrastructure
without it always being me who did (or mediated) the legwork.  (I
continue to plan to get hit by that bus, and I don't intend to put it
off for another whole 25 years.)

> Have you looked at bugzilla-vcs?
> 
>   https://code.google.com/p/bugzilla-vcs/
> 
> Its hook.pl sounds promising, but I haven't even looked at it.

I just glanced at it now, and it does sound promising.  Less comforting
are the facts that it hasn't changed since 2010, that it is a Bugzilla
extension and so messes with the functioning of the Bugzilla installation,
and that it says "can be installed on Bugzilla 3.6.1 or any later version"
while sourceware's Bugzilla is version 4.0.6, which didn't exist until
about a year and a half after VCS was last changed, so believing the
"any later version" claim without new information is a bit of a stretch.

The past solution for CVS had the feature that it didn't involve
fiddling with the Bugzilla installation, though it did use SQL
operations on its backend database, which is in the abstract at least as
scary.  Either way, it seems like something that requires consultation
with whoever it is who is responsible for the Bugzilla installation
on sourceware these days.


Thanks,
Roland