From: "Rémi Cardona" <remi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Bugzilla enhancements wrt AT work
Date: Sat, 15 Mar 2008 19:02:52 +0100 [thread overview]
Message-ID: <47DC0F4C.9070106@gentoo.org> (raw)
In-Reply-To: <200803151737.37065.scel@xdap.org>
Torsten Rehn a écrit :
> Two weeks ago, dirtyepic suggested making some modifications to how ATs and
> developers interact using Bugzilla [1].
>
> <+jakub> scel: basically... instead of KEYWORDREQ/STABLEREQ
> <+jakub> create keywording and stabilization components
> <+jakub> and use flags accordingly there
> <+jakub> bugzilla already has the features, why not use them
> <+jakub> also, nuke things like TESTED and STABLE
Just curious, who would be the default assignee for those 2 new components?
/me will vote for whatever helps to improve Gentoo :)
Cheers
Rémi
--
gentoo-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-03-15 18:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-15 16:37 [gentoo-dev] [RFC] Bugzilla enhancements wrt AT work Torsten Rehn
2008-03-15 17:55 ` Dawid Węgliński
2008-03-15 18:02 ` Rémi Cardona [this message]
2008-03-15 18:31 ` Torsten Rehn
2008-03-15 18:56 ` Rémi Cardona
2008-03-18 6:46 ` Robin H. Johnson
2008-03-18 11:30 ` Robert Buchholz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47DC0F4C.9070106@gentoo.org \
--to=remi@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox