1 |
On Wed, 9 Jan 2013 18:02:01 +0100 |
2 |
Jeroen Roovers <jer@g.o> wrote: |
3 |
|
4 |
> A lot clearer than a single text field littered with keywords would be some |
5 |
> tick boxes, indeed. In fact, it makes me wonder why we use a half-obscured |
6 |
> list in a select field for adding/removing arch teams now. |
7 |
|
8 |
|
9 |
https://bugs.gentoo.org/213514 |
10 |
|
11 |
|
12 |
On Sat, 01 Mar 2008 09:24:36 -0600 |
13 |
Ryan Hill <dirtyepic@g.o> wrote: |
14 |
|
15 |
> On keywording/stabilizing, Bugzilla has a flags feature that might be used to |
16 |
> track what has been tested where. |
17 |
> |
18 |
> Flags have three states: +, -, and ?. + and - are obvious, and ? is a |
19 |
> request. So imagine having a "x86 tested" flag that the maintainer sets to |
20 |
> "?" to request stabilization of their package. An email is sent to the arch |
21 |
> alias notifying them of the request. The arch tester tests it out and sets |
22 |
> the flag to + or - depending on their results. The arch dev stabilizes the |
23 |
> package as normal. |
24 |
> |
25 |
> If we added a "Keyword/Stable Request" component to the "Gentoo Linux" |
26 |
> product we could also have it dependent on that, so only bugs in that |
27 |
> component would display the flags. We can also make it so only people with |
28 |
> editbugs privileges can request or set flags. |
29 |
|
30 |
|
31 |
-- |
32 |
gcc-porting |
33 |
toolchain, wxwidgets learn a language baby, it's that kind of place |
34 |
@ gentoo.org where low card is hunger and high card is taste |