Scmbug
Christian Robottom Reis
kiko at async.com.br
Tue Jun 1 14:41:30 UTC 2004
On Tue, Jun 01, 2004 at 11:47:26AM +0100, Dave Swegen wrote:
> is much better" just isn't going to work. I very nearly didn't bother
> looking any further at that point...
C'mon, Dave. It's a first announcement. :-)
> 2) To be honest, I've pretty much gone off the idea of having the scm
> system fiddling directly with the bz DB. The main problem is that as bz
> starts working with more DB backends, and schemas change, the script is
> going to have to keep up. More maintainance overhead, and you also miss
> out on nice things like sanity checking the SQL. FWIW, the next version
> of the cvs->bz integration will probably talk via the bz web ui (which
> is going to need some work).
I'm probably available to do the backend work to help you here. Do you
have an idea of what sort of interface you need? It's nothing more than
adding a comment to a bug, which requires credentials but not much more.
Note that Justdave has [secretly?] written a bugzilla-change script (in
the line of bugzilla-submit) that already changes a bug report from the
commandline, so I guess you could at least harness some of the posting
code from there. Probably not too hard, I think.
> 5) A common request we have is that when a single commit that covers
> files in multiple directories is made, only one message will be placed in
> bz. I couldn't see anything in your code that dealt with this, but if it
> isn't there you might want to keep that in mind. I still havn't come up
> with a nice clean solution to this.
This isn't a very easy thing to do. My immediate suggestion is grouping
checkins by time and userid and somehow storing it temporarily
"somewhere" (file storage somewhere?), and then periodically sweeping
through that file and adding comments that are, let's say, five minutes
old, to the bug. That requires something daemon-like and isn't a very
clean solution, but then again, lack of atomic commits in CVS is a dirty
problem.
> 7) You might want to think about nicking our bz->viewcvs autolinking
> stuff, and modifying it to cope with the format of your commit messages.
> For a lot of the users of our stuff this a major nice feature.
What about some bz->bonsai autolinking while we're at that? :-)
> The only thing that I believe your system improves on over ours is the
> delivery method, which looks much, much easier to set up and configure.
Delivery method?
Take care,
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331
More information about the developers
mailing list