| 1 |
On 06/11/2022 10.34, Sam James wrote: |
| 2 |
> |
| 3 |
> ... |
| 4 |
> |
| 5 |
> That had two parts: |
| 6 |
> 1. https://github.com/projg2/nattka/issues/72 & https://github.com/projg2/nattka/pull/73 (done) |
| 7 |
> 2. https://github.com/arthurzam/tattoo/issues/1 (not done) |
| 8 |
|
| 9 |
I was waiting for nattka-0.4 (which returns the field value) and was |
| 10 |
hoping to wait until it becomes stable, so it will be able to upgrade |
| 11 |
nattka on all devboxes easily and just use new API. Seeing this |
| 12 |
conversation, made me understand that it is desired to do it ASAP, so I |
| 13 |
added it now with a little ugly code around (import guards to check that |
| 14 |
nattka supports the new field). |
| 15 |
|
| 16 |
So currently tattoo skips all bugs marked with Manual testing. |
| 17 |
|
| 18 |
|
| 19 |
I also plan to create a small dashboard showing special cases of Arch |
| 20 |
Testing bugs, such as: |
| 21 |
|
| 22 |
1. Bugs with only one arch remaining |
| 23 |
2. Bugs blocked by blocker bug |
| 24 |
3. Bugs without any info and activity (not blocked, untouched, not done) |
| 25 |
|
| 26 |
This is in hopes to have a more organized and priority bugs, to mitigate |
| 27 |
cases when something somewhere failed, and we lose the bug until pinged. |
| 28 |
|
| 29 |
My current plan is to have a script that generated a HTML file that I |
| 30 |
will host on ~dev space, and will have a scheduled process to regenerate |
| 31 |
the HTML. I'm still planning the solution and how to schedule it, so no |
| 32 |
promises :) |
| 33 |
|
| 34 |
-- |
| 35 |
Arthur Zamarin |
| 36 |
arthurzam@g.o |
| 37 |
Gentoo Linux developer (Python, Arch Teams, pkgcore stack, GURU) |
Archives