1 |
On Mon, Aug 15, 2016 at 3:03 PM, Kristian Fiskerstrand <k_f@g.o> wrote: |
2 |
> Could you please elaborate a bit? In particular from perspective of (i) |
3 |
> integration into current workflow, (ii) complexity in application |
4 |
> maintenance/hosting (iii) cost/benefit considerations |
5 |
|
6 |
Well, I think stabilization (and, to some extent, keywording) is a |
7 |
very different process from handling bugs and feature requests. It |
8 |
would be great if we had tooling that focuses on these instead of |
9 |
trying to fit into the bug tracker. It would entail a different |
10 |
workflow, obviously, but I think that's a plus in this case, and we |
11 |
could make sure we have the command-line tools to make it easy to work |
12 |
with. |
13 |
|
14 |
Development/maintenance/hosting is an issue, though it's a bit hard to |
15 |
say something definitive about it before there's more of a plan of how |
16 |
such a tool could work. It's enough of a pain for me that I could see |
17 |
myself investing some time in development. |
18 |
|
19 |
Perhaps some kind of middle ground would be to handle this stuff in a |
20 |
separate Bugzilla product, and then making sure we have some tooling |
21 |
around that to better present the data. |
22 |
|
23 |
Cheers, |
24 |
|
25 |
Dirkjan |