17 messages in org.apache.maven.devRE: how we handle JIRA versions
FromSent OnAttachments
Brett PorterAug 1, 2007 9:47 am 
Dennis LundbergAug 1, 2007 12:31 pm 
Brett PorterAug 1, 2007 7:00 pm 
Jason van ZylAug 1, 2007 8:21 pm 
Christian GruberAug 1, 2007 8:25 pm 
Brett PorterAug 1, 2007 8:37 pm 
Jason van ZylAug 1, 2007 8:51 pm 
Brett PorterAug 1, 2007 8:55 pm 
Brian E. FoxAug 1, 2007 9:01 pm 
Brett PorterAug 1, 2007 11:11 pm 
jaso...@gmail.comAug 1, 2007 11:24 pm 
Brett PorterAug 1, 2007 11:37 pm 
Dennis LundbergAug 2, 2007 3:11 am 
Dennis LundbergAug 2, 2007 3:20 am 
Jason DillonAug 2, 2007 3:28 am 
Brett PorterAug 2, 2007 3:29 am 
Vincent SivetonSep 12, 2007 3:54 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:RE: how we handle JIRA versionsActions...
From:Brian E. Fox (bri@reply.infinity.nu)
Date:Aug 1, 2007 9:01:41 pm
List:org.apache.maven.dev

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.

--------------------------------------------------------------------- To unsubscribe, e-mail: dev-@maven.apache.org For additional commands, e-mail: dev-@maven.apache.org