Vlastimil Babka [EMAIL PROTECTED] wrote:
Or maybe implement new bugzilla keywords, like STABLEREQ and
KEYWORDREQ which would be added to the respective bugs. Then you (the
maintainer) can easily create (and save) an advanced search that will
filter them out, while still being able to check
On Wed, 2007-04-18 at 07:39 -0600, Jim Ramsay wrote:
Vlastimil Babka [EMAIL PROTECTED] wrote:
Or maybe implement new bugzilla keywords, like STABLEREQ and
KEYWORDREQ which would be added to the respective bugs. Then you (the
maintainer) can easily create (and save) an advanced search that
Chris Gianelloni wrote:
On Wed, 2007-04-18 at 07:39 -0600, Jim Ramsay wrote:
Vlastimil Babka [EMAIL PROTECTED] wrote:
Or maybe implement new bugzilla keywords, like STABLEREQ and
KEYWORDREQ which would be added to the respective bugs. Then you
(the maintainer) can easily create (and
On Tue, Apr 17, 2007 at 09:50:26PM +0200, Stefan Schweizer wrote:
On 4/17/07, Doug Goldstein [EMAIL PROTECTED] wrote:
Bugs that are created for the purpose of getting arches to keyword or
stabilize a particular package should initially be assigned to the
herd/maintainer of said package with
On Tue, 2007-04-17 at 21:50 +0200, Stefan Schweizer wrote:
It would be cool to implement a [EMAIL PROTECTED] alias just to
assign those bugs to so that we maintainers do not need to see them.
While you may not find them useful, there have been 3 recent occasions
of user requesting things get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan Schweizer wrote:
It would be cool to implement a [EMAIL PROTECTED] alias just to
assign those bugs to so that we maintainers do not need to see them.
Or maybe implement new bugzilla keywords, like STABLEREQ and KEYWORDREQ
which would be
