Hi again,

I'm now ready to take a look at this.  Kristis, could you give me a little
guidance please?  I've read through
http://bugzilla.mkgnu.net/show_bug.cgi?id=948 and assume that
Scmbug/Daemon/Bugzilla.pm should be the only thing that needs changing.
From there, I should make use of the bugzilla interfaces, rather than going
direct to the database.  This is where I'm a little unsure of the best
approach.... the whole Bugzilla.pm file seems to assume that we'll be going
direct to the database, it seems that it'll be some pretty messy code to use
that as a base.  Would a Bugzilla3.pm be workable?  (I have no idea what the
best approaches to perl are).

Secondly, looking at http://www.bugzilla.org/docs/tip/html/api/ there is no
mention of Bugzilla::Bug - am I missing something here?  The code runs fine
up to line 46:
 print "pid:".$product->id."\n";
but generally the concept looks good.

I'd like to do this this week, so if people can help me with the above we
should be able to have some sort of bugzilla 3 support soon.

cheers,
dim


On 5/23/07, Dmitri Colebatch <[EMAIL PROTECTED]> wrote:

Hi guys,

On 5/17/07, Kristis Makris <[EMAIL PROTECTED]> wrote:

> On Wed, 2007-05-16 at 10:44 -0700, Jeremy Truax wrote:
> > Are there any plans in the works for integrating with bugzilla 3.0 at
> > all yet? I have users asking to upgrade from 2.20 and before I do I
> > wanted to make sure Scmbug is compatible.
>
> Hi Jeremy. This has been requested before, and it looks like some work
> begun on it (by other people)
>
> http://bugzilla.mkgnu.net/show_bug.cgi?id=948
>
> I won't be implementing this, so unless you or someone else commits to
> adding this support and sending patches then there's no timeframe for
> it.


I too have users wanting to upgrade and am prepared to take a look at
doing the work myself, although I'm no perl expert so it might be slow
going!

cheers,
dim

_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users

Reply via email to