Hi Oliver, On 12/27/07, Oliver Schäfer <[EMAIL PROTECTED]> wrote: > > Hello Kristis, > > I really need your support to finsish these issues (others are > welcome too):
I'm sorry for the late replies. Something else has priority until mid-January. But I'll do my best to stay in touch. http://bugzilla.mkgnu.net/show_bug.cgi?id=948 > Bugzilla 3 code is quite stable, those two methods are still buggy: > integration_get_bugs: How can I test it? What are the use cases? Use the merger tool scmbug_merge. It issues an activity_get_bugs that eventually calls this. Please try to look it up in the manual which documents two use cases. You essentially need to call this tool with --merge-bugs=<bugs_list>, and the list of bugs supplied in <bug_list> will make their way into integration_get_bugs. The purpose of this function is to return the comments/changelist and status/resolution/priority/etc of each of those bugs in order to call the SCM tool to merge these changes to a branch. Merging is not implemented in the merger yet. integration_get_vdd: Still needs rework, have you an example output? > At the moment it's generated but no bugs in it. I'm afraid I don't. I tried to produce one and got no bugs in response either. I'd recommend you look at the existing Bugzilla.pm.in source for 2.20.x > http://bugzilla.mkgnu.net/show_bug.cgi?id=1061 > This is almost done. It's generated dynamically once for each > instance. I don't think we have to look up each time we use it, do we? I think we do :) Else people would have to restart the daemon. Only retrieve this list dynamically if a resolution status will be processed for activity_verify and activity_commit.
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
