Hi Oliver, You are staying busy!
On Sun, 2007-12-23 at 10:29 +0100, Oliver Schäfer wrote: > Hello Kristis, > > I want to summarize my evaluation of this issue. First of all, these > are the 'bugs' I've found for this issue. > > http://bugzilla.mkgnu.net/show_bug.cgi?id=547 > http://bugzilla.mkgnu.net/show_bug.cgi?id=948 > http://bugzilla.mkgnu.net/show_bug.cgi?id=1061 I'd rather we addressed bug 1061 last. If we can implement resolutions with a fixed $bug_status_map, adding the support to read this map at run time can be addressed as a separate step. > http://bugzilla.mkgnu.net/show_bug.cgi?id=1082 > > I've considered following options for implementation: > > 1. Write our own code > 2. Wait for Bugzilla 3.2 > 3. Use Bugzilla's email interface > > Option 1: Wouldn't be a trivial task because we have to care about: > - Bug activity logs > - Timetracking issues > - Database integrity > - User and group permissions (Bugzilla) > - Support and maintenance of own code (probably most important) I would go for a combination of Option 1 and 2. Option 1 first, in the sense that we just have to write our own code for bug resolution for versions 2.14.x, 2.16.x, 2.18.x, 2.20.x, 2.22.x. As for 3.0.x, and onward, I understand an attempt to provide an API was underway by the Bugzilla folks. If we can use it, great! If not, lets implement our own code for 3.0.x too, and hopefully can use the API at 3.2.x. > Option 2: Would be the best solution, because Bugzilla 3.2 will offer > all the API methods we need. But to have some intermediate solution > for 3.0 users I've found ... > > Option 3: Use email_in.pl contributed by bugzilla. This may also work > for older bugzilla versions, but I would focus on bugzilla 3.0.x. I'd rather we didn't use an asynchronous change mechanism that may fail without the Scmbug backend knowing it did. This was one of the reasons Scmbug was designed to have synchronous access to the backend database. So it can be certain of the state of things. How do you feel about all this ?
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
