[jboss-dev-forums] [Design of JBoss jBPM] - Re: meeting context

Wed Oct 8 13:40:08 EDT 2008

Yes, a good result of the meeting would be a set of API interfaces/classes that everybody can agree on plus a set of CTS test cases that exercises the API.

The 1-Jan-2009 jBPM4 release should then provide an implementation of that agreed API.

In Jan we meet again and set the scope for 1-Mar and so on ...

If we can stay focused on correctness and ease of use of the API it will be possible to move quickly and enlarge the scope of functionality for given release cycles. This will hopefully rather sooner than later lead to a jBPM4 release that can replace the current jBPM3 product.

The replacement criteria (and I say it again) is a product that passes the CTS through the API. The functional scope of that product must  be at least that of jBPM3.

Key to good progress is to stay focused on what can actually get achieved in a given release cycle plus delivery on an unconditional basis.

A good indicator of this "we will deliver as promised" principal, is the upcoming jBPM-3.3.0.GA release. The team succeeds if promised functionality is unconditionally available by a certain date, sufficiently documented and properly integrated in automated QA. 

You can monitor progress on the JIRA road map panel

https://jira.jboss.org/jira/browse/JBPM?report=com.atlassian.jira.plugin.system.project:roadmap-panel

... the remaining work load per individual with this report ...

https://jira.jboss.org/jira/secure/ConfigureReport.jspa?filterid=12311991&mapper=assignees&selectedProjectId=10052&reportKey=com.atlassian.jira.plugin.system.reports%3Asinglelevelgroupby&Next=Next

... and recent changes to the project here ...

http://jbpm.dyndns.org:8280/hudson/job/jBPM3-Matrix/changes

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

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