[hylafax-devel] Re: ANNOUNCE - bug tracking system

[Jay R. Ashworth <jra@baylink.com>]

On Wednesday, August 16, 2000, at 11:00:59 AM, Mail Delivery Subsystem wrote:
> On Wed, Aug 16, 2000 at 09:44:38AM -0400, Jay R. Ashworth wrote:
>> On Wednesday, August 16, 2000, at 2:09:08 AM, Joe Phillips wrote:
>> > Specifically, please suggest more components of the HylaFAX 'product.'  I've
>> > already added hfaxd, sendfax and faxstat components but I'm sure there are
>> > more.
>> 
>> 'packaging'.  I tried to install the beta2 binary RPM on rh6.1 the
>> other night, and had several problems with dependencies and
>> collisions.

> I'm not sure how to put 'packaging' in the database.  Each component in
> bugzilla has a default maintainer, the user that gets notification of a
> bug in his/her component.  The RPM maintainer is likely to be different
> than the Debian deb or Solaris pkg maintainer.  We may not want to lump
> all package types into a single group for bug-tracking purposes.  Then again,
> we may want to do that.

You're right; we wouldn't.  I guess rh5-rpm, rh6-rpm, mdk7-rpm, deb,
etc... (if indeed the rpmage needs to be broken down that far; it may
not; I'm not a big rpm builder.  :-)

> Bugs can always be forwarded to another user in the system.  So lumping
> all packages into a single component wouldn't necessarily be all that bad
> since the 'packaging' maintainer could forward the bug to the proper
> bugzilla user for different package types.

Yeah, but it would probably be easier to...

> Alternatively, I could make a separate 'product' for 'HylaFAX Binary Packages' 
> with sub-components for each package type.

...do that.

> I've added some more components from the man pages however I do not know
> how up-to-date the web man pages are or which man pages should map to
> components in bugzilla.  I request the group's assistance in figuring
> out what components should be listed in bugzilla.  Follow this link
> http://bugs.hylafax.org/bugzilla/describecomponents.cgi?product=HylaFAX
> for a listing of current components.

I'm thinking that documentation should probably be a product, with
'man pages' and 'other docs' as the first components; I'm perfectly
willing to volunteer for that product.

> We'll also need to assign "default owner" to each component as we begin
> to populate the database.  Any volunteers?

Ah.  See above.

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra@baylink.com
Member of the Technical Staff     
The Suncoast Freenet
Tampa Bay, Florida     http://baylink.pitas.com                +1 727 804 5015


____________________ HylaFAX(tm) Developers Mailing List ____________________
 To unsub: mail -s unsubscribe hylafax-devel-request@hylafax.org < /dev/null