[gentoo-dev] Re: Bugzilla isn't just for bugs [reminder]

[Duncan]

Michael Cummings posted <20050720075942.6b6241a0@×××××××××××.mil>,
excerpted below,  on Wed, 20 Jul 2005 07:59:42 -0400:

> I can't speak for other developers or herd maintainers, but if you have
> been using a perl package that is ~arch masked and think its as good as it
> gets, please file a 'bug' on bugzilla saying so. I've seen folks lately
> doing it for amd64 keywording - yay! But we also need that kind of
> feedback for mainstream keywording. Otherwise we get into the situation
> that any dev has faced - you have a package ~arched, you use it for a
> month or three, no problems, but then it languishes in ~arch land because
> you don't have the gentle reminder that others think its ready for prime
> time too.
>
> I guess the drift I'm trying to making (and why I separated this out from
> that longer thread) is to encourage the folks on this list, being a
> development list and all, to please post on bugzilla for both the good and
> the bad of any ~arch package your using - any feedback helps us churn out
> a newer Gentoo for you faster ;)

Since it seems this request is gaining traction, I'd suggest the format
for such bugs be standardized, particularly summary line, so as to prevent
duplication as much as possible, while allowing "works here also" and
"does NOT work here because of bug #xxxxxx" on the same bug.  From our
experience with amd64 multilib-strict bugs, standardizing the name can be
/very/ helpful.

Perhaps a summary line format something like:

[keyword stable] package-x.y.z

Note that bugzilla has the TESTED and STABLE keywords, but they are
reserved for use by ATs (and presumably devs). The AT guidelines
(available for amd64 ATs here:
http://www.gentoo.org/proj/en/base/amd64/tests/index.xml ) specifically
mention testing "every conceivable permutation", and because not just
anyone becomes an AT (the ebuild quiz must be passed, among other things),
reserving special keywords for ATs makes sense since they /should/ be
fairly reliable.  Ordinary user testing might not be quite so reliable
(tho one should expect most but not all here are devs, and theirs would
be), and keywords aren't quite so obvious to users, so the distinction
should be useful.  Additionally, will these keywords show up on the
initial pre-filing searches?

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-dev@g.o mailing list