1 |
On Mon, Aug 15, 2016 at 03:53:26PM +1200, Kent Fredric wrote: |
2 |
> On Mon, 15 Aug 2016 11:45:22 +0800 |
3 |
> Jason Zaman <perfinion@g.o> wrote: |
4 |
> |
5 |
> > IN_PROGRESS == we've put the fix in the git repo |
6 |
> > RESO/TESTREQ == new release and in ~arch |
7 |
> |
8 |
> TESTREQ was incidentally my first thought. Only needs me to study how much that's already used |
9 |
> and whether or not existing bugs with that flag meet that description or not. |
10 |
> |
11 |
> |
12 |
> However, a distinction between IN_PROGRESS and RESO/TESTREQ is not possible here, |
13 |
> because "in git" means "You'll get it if you sync >1h from now" |
14 |
|
15 |
Oh, I meant this is for our policy stuff. which is in |
16 |
hardened-refpolicy.git and then every few weeks we make a release and |
17 |
bump all the packages in sec-policy/selinux-*. For things that do not |
18 |
need an actual release we just skip INPROG and go straight to TESTREQ |
19 |
when we fix the ebuild in the tree. |
20 |
|
21 |
The important part to me is that RESO/FIXED should only mean fixed when |
22 |
the problem is fixed in the stable tree too. There has to be another |
23 |
state before FIXED that is for ~arch. If the package is not stable on |
24 |
any arch then of course it is FIXED as soon as ~arch is fixed. |
25 |
|
26 |
> IN_PROGRESS can thus only mean something about it being worked on but not yet pushed |
27 |
> to the main git repo. (ie: overlays, private repos) |
28 |
> |
29 |
> But I would rather it part of the primary resolution path, not a mere property of the resolution type. |
30 |
> |
31 |
> Because its easier to say: |
32 |
> |
33 |
> UNCONFIRMED -> CONFIRMED -> INPROGRESS -> INVCS -> STABLE |
34 |
> |
35 |
> Than |
36 |
> |
37 |
> UNCONFIRMED -> CONFIRMED -> INPROGRESS -> (RESOLVED/TESTREQ) -> (RESOLVED/FIXED) |
38 |
|
39 |
They are roughly equivalent, yeah. But I prefer TESTREQ because its |
40 |
easier to see in the bug list page. You can of course choose which items |
41 |
are shown in the list in bugzilla but resolution is already there so no |
42 |
need to add an extra column. |
43 |
|
44 |
-- Jason |