[Koha-bugs] [Bug 30998] [DOCS] Managing documentation tasks - simplify processes and integrate more with the development process

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30998

--- Comment #16 from Victor Grousset/tuxayo <victor at tuxayo.net> ---
The topic came up on today's meeting.

Here is, like Arthur did, ideas about how to follow-up on the topic of
documentation:

Maybe we could have a status "Failed QA, missing documentation" which the
documentation team could also unblock taking the oldest ones first. So it does
not get stuck forever on that.
But that still too much delay to get merged and can require rebases.

Another idea is to do it after the patch is merged to master. But it's the dev
that does it and the documentation team if that takes too long. We can expect
this to happen often since there isn't the incentive to have the patch merged
anymore. But compared to the new workflow now from this ticket, it should cause
part of the developers to do that and make less work for the documentation
team. Would that work?

-- 
You are receiving this mail because:
You are watching all bug changes.