Re: [gnome-love] Adding a new application to bugzilla

[Telsa Gwynne <hobbit aloss ukuu org uk>]

Getting packages into bugzilla:

On Mon, Jul 02, 2001 at 02:15:39PM -0400 or thereabouts, Kevin Vandersloot wrote:
> Yes procman. I'm glad someone is on it for me, but for future reference (for
> the gnome-love archives) what is the proper procedure for adding an entry?

Mail bugmaster gnome org  This is a mailing list of half a dozen (or
more?) folk with the requisite permissions to do it. We are -fairly-
responsive: like many mailing lists, there's "Oh, I thought someone
else had done it" oversights at times. 

Here's some things to include (it looks a lot worse than it is, I
just tried to include everything for the archives :))

name of the product (bugzilla category)
        * usually the CVS module. 
one-line description of package
        * This shows up in bugzilla and in bug-buddy's "what product"
        screen, so pick something that makes sense to everyone in
        a single line (and good luck at trying to!)
        * I have seen "This is NOT for..." for packages people keep
        misassigning bugs to before now :) 
released version(s) of package
        * unspecified is generally a good idea for people who don't know.
        * tarball version(s) so far. You can do things like "pre-1.0" if
        you know you had a bunch of quick releases before a 1.0 you 
        actually announced and you don't want ten tiny categories of
        really old stuff. 
components in the package
        * docs - required (the component is required, you don't have to
        have written them just yet, we'll just put bug number one as "no
        docs" :)) 
        * general - required
        * whatever is appropriate for your package: perhaps "app-backend"
        "app-frontend" and "app-libs". Or "neatapp-1", "neatapp-2", and
        "neatapp-3" for a package that has a bunch of programs in it.
one-line description for every component
        * sorry, but we need this too :)
        * again, people use these to decide where to report a bug. So
        refrain from "XML BNF ext3-parsing API buzzword" if it's a
        component or product for non-technical users. (If it's _for_
        hackers, you can get away with it, obviously.) If it's for 
        end-users, "This is the user-visible configuration screen" and
        "this is the configurator backend you shouldn't see" might be
        better. Well, perhaps not that simple, but you get the idea. 
an owner for every component
        * this owner is the one who gets to edit/modify/close etc all
        bugs in that component.
        * the address has to be a bugzilla account, and has to exist,
        so make it first. 
        * there can normally only be one address who owns a component
        (but see below)
        * if there are a bunch of people working on this package and
        they're going to share all the components together, Martin B
        wrote a little way around the "one owner for one component"
        thing. In the halloween module of CVS lives a maint-aliases.txt
        file (halloween/bugzilla.gnome.org/maint-aliases.txt). Look at
        it and you'll get the idea. Format is:
        bugzilla package: account1, account2, account3
        Add yer package and accounts, cvs commit, and wait an hour for
        cron to catch it. This will create a pseudo-account called
        <package>-maint bugzilla gnome org, who can own the component
        for that bunch of people. Only problem with this is that we
        have to add a whole lot of privs to every single name on the
        list then, which takes a whole... oh. extra second per person? :) 

If you do not include these, I will just email you anyway asking for
them -- or I shall make them up :) 

Telsa