On Jan 30, 2009, at 4:54 PM, Craig L Russell wrote:
Looking at JIRA, the Geronimo workflow implements a Review-Then-
Commit workflow, which isn't what we want.
Somethings wrong here.... we haven't had review-then-commit for a long
time and I don't think jira was enforcing it.
The only suitable workflow seems to be no-reopen-closed, patch-avail
workflow that, as its name suggests, makes two changes to the
standard workflow:
It does not permit closed bugs to be re-opened, encouraging the
filing of new bugs; and it adds a "patch available" status.
Preventing reopening closed bugs is dumb IMNSHO :-) unless you can
edit everything about a closed bug. Otherwise the fixed in and
component fields are almost certain to be wrong on many many bugs.
Is this a change that the community wants to make? Or is a note
dropped to the dev list enough, as Donald has done?
I don't know how geronimo got its patch available checkbox but since
we have it and can reopen bugs.... there must be a way you can too :-)
thanks
david jencks
Craig
On Jan 30, 2009, at 1:48 PM, Donald Woods wrote:
I have attached patches to both JIRAs and unassigned them from me,
but thought I'd drop a note to everyone as there is no "Patch
Available" field like we used in Geronimo to denote JIRAs from
contributors that were ready for review.
-Donald
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:[email protected]
P.S. A good JDO? O, Gasp!
