SCM Integration support in Bugzilla

Kristis Makris mkgnu at
Wed Aug 4 19:24:06 UTC 2004

> > 2.16.x, Bz 2.18.x and anything in the future. I'd like you to force me
> > to use a single package (e.g. that is guaranteed to
> > never break the bugtracking-backend integration, and that we all upgrade
> > accordingly when schema changes occur.
> It ain't gonna happen.  The API that exists in 2.14/2.16 is rapidly 
> going away.  We can probably agree on something for 2.20 and forward 

This is a fair response. If you don't mind, I'd like to file a bug for
this. I'd like us to agree on something for 2.20 and forward that will
be persistent. Bugzilla just has to decide how it wants to be integrated
:) Dave Swegen had mentioned some thoughts for integration through the
web over a .cgi, using an admin account. He also had some ideas on
storing the SCM username within Bugzilla. Whatever you folks decide,
I'll go with. But please, lets address this.

> going away as soon as we can make them do so; so API compatibility 
> between 2.20 and 2.16 is probably not a possibility.

Fair enough. Since I know what changed in 2.18 and have a fix for that,
I can support that within Scmbug for now.

More information about the developers mailing list