On 02/08/2007, at 2:02 PM, Brian E. Fox wrote:
It'd be nice to enforce it now, but I'm not prepared for that kind of
pain :) If someone else who's done more jira workflowy things wants
to try their hand, please do. Otherwise, I figure if we at least have
a stated pattern in agreement, if we see regular violations we should
either review the rule, or enforce it at that point.
I setup and maintain Jira at my day job so I can help with
workflows if
needed. It's a major PITA currently to change workflows that are in
use
(and we have a boat-load of projects here at maven). I've been
trying to
get Atlassian to commit to fixing it but no luck yet.
Yeah, we can just get something working with MNG then migrate later
(I know you have to basically create a new one and move everything to
it - this is our time to go back to being Maven instead of Maven new
perhaps :)
One thing that might be good to start with is adding a "need info"
state: http://mail-archives.apache.org/mod_mbox/maven-dev/200706.mbox/
%3C46...@apache.org%3E
- Brett
17 messages in org.apache.maven.devRe: how we handle JIRA versions
