[jbpm-dev] [Design of JBoss jBPM] - Re: jBPM project structure and direction

thomas.diesler@jboss.com do-not-reply at jboss.com
Fri Sep 26 04:21:04 EDT 2008


Hi Joram, 

part of how we make sure to achieve our goals is good usage of JIRA. For every given 8 week release cycle, we have JIRa freeze after 2 weeks and code freeze after 6 weeks. The remaining 2 weeks is for QA and documentation.

In JIRA you should see reliable release dates associated with a given version and details of what remains to do be done is in the JIRA road map.

i.e. for jbpm-3.3.0.GA there are now 58 issues that remain to get resolved

https://jira.jboss.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10052&fixfor=12312435

So in a way, the above post is rather conservative and uses a lot of words to say: "Let's get these 58 issues resolved in time" ;-)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178989#4178989

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178989



More information about the jbpm-dev mailing list