Quoting Ciaran McCreesh <[EMAIL PROTECTED]>:
Currently, things assigned to maintainer-wanted get the following
keywords (bugzilla, not ebuild):
* EBUILD if an ebuild is attached
* REQUEST if an ebuild is requested
Ah. I didn't know this was part of the bugzilla policy.
I've been going through the EBUILD list at random and providing lists of
things that need to be fixed before the ebuild can be considered for
inclusion. The WONTFIX resolution along with a comment asking for the
submitter to reopen with a fixed ebuild is used when problems are found.
Note that I'm being pretty strict about quoting, style etc, partly
because one easy way of improving tree QA is by making sure that new
entries are of a high standard and partly because it would be nice for
herds to be able to get a perfect, probably no changes needed ebuild.
Sure, some of the existing tree is far from ideal, but that's no excuse
for adding new shoddy things.
What I'd like is a new keyword (bugzilla, not ebuild) for indicating
that a developer has done a check on an ebuild and is satisfied that
the ebuild is fine from a style perspective. This does **not** mean
that the developer has tried to actually merge the package. There're
all kinds of things for which I can say "the ebuild looks good", but
not so many for which I can say "the ebuild looks good and installs
something that works", since a lot of them have insanely long
dependency lists or specific hardware requirements. Can anyone suggest
a name? Best I can come up with is STYLE_CHECKED(nickname)...
Good idea. That means one could distinguish:
1/ Freshly submitted ebuilds that haven't been looked at yet (open bugs,
assigned to maintainer-wanted, where keywords field contain the EBUILD
substring but doesn't contain the STYLE_CHECKED substring),
2/ Submitted ebuilds that have already been looked at, but need some
rework to be added to the tree (closed bug, resolved as WONTFIX,
assigned to maintainer-wanted, CC-ed to the concerned herd(s), where
keywords field contain the EBUILD and the STYLE_CHECKED substrings),
3/ Submitted ebuilds that have been verified with success, but haven't
been tested nor included int the tree yet (open bugs, assigned to
maintainer-needed, CC-ed to the concerned herd(s), where keywords
contain the EBUILD and the STYLE_CHECKED substrings).
That makes a lot of things to remind when changing bug states.
Hopefully it will reduce herd loads significantly if it can be ensured
that they're only sent high quality ebuilds...
Can this be added to the bugzilla-howto, whatever the final decision is?
Imho, there are several points missing in this howto, like security
status whiteboard policy (which can be found in the Vulnerability
Treatment Policy), keywords policy (I wasn't aware of the EBUILD vs
REQUEST for maintainer-wanted) and priority (how is it really used?).
That would be great, especially for new developers as well as users to
better understand what's going on with the bugzilla.
Furthermore, could the bugzilla bug lifecycle
(http://www.bugzilla.org/docs/2.18/html/lifecycle.html) be referenced
in the bugzilla-howto, or even better, updated with Gentoo workflow
characteristics and included?
Any comments? Thanks,
--
Julien Allanos (dju`)
Gentoo Linux Developer (web-apps)
GnuPG key: 0x1EC6C6C2
--
gentoo-dev@gentoo.org mailing list
