jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From KÖLL Claus <C.KO...@TIROL.GV.AT>
Subject AW: Using the patch-available workflow in Jira (Was: Jackrabbit 1.6 release plan)
Date Tue, 26 May 2009 14:40:42 GMT


>This workflow is just like what we have now with two differences:
>1) A closed issue can't be reopened. This works well for our Jira
>practices, as we normally "resolve" an issue when it's fixed and
>"close" it when the fix is released. After that the issue should no
>longer be reopened to avoid
>2) There's a new optional issue status called "patch available". A
>contributor can move an issue from "open" to "patch available", and a
>committer can then move it either back to "open" if the patch is
>rejected or "resolved" if the patch is accepted. The good thing about
>this is that with this extra status we can easily list just those
>issues that have patches waiting for review.
>Any objections to changing the workflow? If not, then I'll change the
>Jira settings accordingly.

View raw message