| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Jim Ramsay wrote: |
| 5 |
> Chris Gianelloni wrote: |
| 6 |
>> On Wed, 2007-04-18 at 07:39 -0600, Jim Ramsay wrote: |
| 7 |
>>> Vlastimil Babka <caster@g.o> wrote: |
| 8 |
>>>> Or maybe implement new bugzilla keywords, like STABLEREQ and |
| 9 |
>>>> KEYWORDREQ which would be added to the respective bugs. Then you |
| 10 |
>>>> (the maintainer) can easily create (and save) an advanced search |
| 11 |
>>>> that will filter them out, while still being able to check them |
| 12 |
>>>> in a different search. Might be also useful for arch teams to |
| 13 |
>>>> separate stabling and keywording bugs? |
| 14 |
>>> I think that's a great idea. Who do we bug to get this in there? |
| 15 |
>> File a bug in the Bugzilla component. |
| 16 |
>> |
| 17 |
> I hear and obey: |
| 18 |
> |
| 19 |
> http://bugs.gentoo.org/show_bug.cgi?id=175103 |
| 20 |
|
| 21 |
Bug was fixed yesterday, keywords added, so to let you know. I would of |
| 22 |
course love to go now and add these keywords to all my (java) current |
| 23 |
bugs but not wanna get wrath of arch teams for bugspam. So I'm asking if |
| 24 |
they would tolerate it (especially amd64, ia64, ppc, ppc64, x86 :) or |
| 25 |
not. Or arch teams could maybe temporarily turn off bugzilla notify on |
| 26 |
keyword change for some time (week?) so everyone interested can add |
| 27 |
these keywords without bugspam? Any better ideas? |
| 28 |
- -- |
| 29 |
Vlastimil Babka (Caster) |
| 30 |
Gentoo/Java |
| 31 |
-----BEGIN PGP SIGNATURE----- |
| 32 |
Version: GnuPG v1.4.7 (GNU/Linux) |
| 33 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 34 |
|
| 35 |
iD8DBQFGWVw6tbrAj05h3oQRAkGRAKCKu+2COeN+iKkm6WVgbO3SCg6mIACgjFgj |
| 36 |
b+GTTH1Lpmz4PG3uiqiCn6I= |
| 37 |
=YSKc |
| 38 |
-----END PGP SIGNATURE----- |
| 39 |
-- |
| 40 |
gentoo-dev@g.o mailing list |
Archives