Re: [Fwd: Re: Apache switching to Scarab]
- From: Andrew Sobala <aes gnome org>
- To: Luis Villa <louie ximian com>
- Cc: gnome bugmaster <bugmaster gnome org>, GNOME Bugsquad <gnome-bugsquad gnome org>
- Subject: Re: [Fwd: Re: Apache switching to Scarab]
- Date: 25 Jul 2003 18:56:53 +0100
On Fri, 2003-07-25 at 15:41, Luis Villa wrote:
> The end of this (discussing the code modularity of bugzilla 2.17.4)
> makes me think that maybe we should skip 2.16 and go directly to 2.17-
> sounds like it might make some of the bug-buddy stuff much easier.
> Anyway... just a random morning thought. :)
>
> Luis
>
/me attacks Luis with a large trout. With big, nasty teeth :-)
Don't forget that bugzilla-new currently has working [1] bug-buddy
import support. 2.17 has some great features, but it's a moving target;
2.16 has working code in our CVS and could even be ready for mainstream
testing soon [2]. I don't think we should regress all that work and
start a brand new port. Yet.
> -----Forwarded Message-----
> From: David Miller <justdave syndicomm com>
> To: developers bugzilla org
> Subject: Re: Apache switching to Scarab
> Date: 24 Jul 2003 14:56:21 -0500
>
> On 7/24/2003 3:43 PM -0400, Yannick Koehler wrote:
>
> > Could you explain to me how Bugzilla is modular? From my experience with it,
> > bugzilla is all but modular. A change at one place require figuring out its
> > side-effect because it is exactly NOT modular.
> >
> > A module is something contained that if you change you can easily know its
> > impact because it has defined input and outputs or services.
>
> Bugzilla's code has changed a LOT in the last year. 2.16.x is for the most
> part NOT modular. 2.17.1 and onwards have been a little bit, and have
> gradually been increasingly so. The bulk of the code has been getting
> moved into Perl module files (.pm) with defined objects, and methods and
> properties on those objects.
>
> A Bug is an object (though it's read-only at the moment - being able to
> write to a Bug object is on the intended features list).
^^ If a bug is read-only, bug-buddy import isn't massively helped by
code modularity yet?
> An Attachment is an object.
> A User is an object.
> The authentication process is now handled by pluggable modules.
> A Search/Query is an object, although the input/output to the Search object
> is still a little fuzzy (it still depends on CGI input for example, rather
> than taking arbitrary data). That'll eventually be fixed, too.
--
Andrew Sobala <aes gnome org> [3]
The lighting designer is expected to be a master of art, science,
history, psychology, communications, politics and sometimes even
mind reading. -- Stage Lighting Design 101
[1] The unknown bugzilla gnome org stuff isn't in there yet. But
I don't actually expect it to be dramatically different to 2.10.
[2] This assumes I, or other people, have time to actually get it
working. But the timescale to getting 2.16 working is dramatically
shorter than staring a whole new 2.17 port.
[3] Who is going on holiday tomorrow, so probably won't see the end of
this thread.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]