[Koha-devel] Another bug status

[Francois Charbonnier]

Recently, I did some sign-off on Jonathan.s patches. I agree with Nicole 
that something is missing in the workflow.
To me, if I can't sign-off a patch because it doesn't work as expected, 
I see just two options : In discussion and failed QA.
Since it's not QA, I don't use failed QA. In discussion doesn't seem 
right either. Usually, I don't want to talk about the feature but just 
say " Hey, I tried but I can't sign-off because <insert why>. Could you 
fix it so I can try again?"
I like the failed sign-off option.
My2cts


Le 2015-03-04 09:36, Mirko Tietgen a écrit :
> I think what would be more helpful than yet another status is
> consensus about when to change it and who does it. Often someone
> does not want to sign off for reasons found in the comments, but
> also does not want to keep others from doing it, so needs signoff is
> kept. Then the next 20 people come and see the discussion, so they
> don't sign off because someone had objections.
>
> So there should be a rule when to change it. Do I change it when I
> raise concerns? Should the next person change it that agrees not to
> sign off? Should it be done after a certain period of time?
> (something that bug wranglers could check regularly maybe)
>
> There has to be a signal to the submitter that s/he has to do
> something (react to comments, submit another version, maybe
> something else) instead of keeping needs signoff for months.
>
> Let's not have more options to not change the status to, but agree
> on when to change it.
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/