Re: [jbpm-dev] Proposal for jBPM5 first release

Hi Kris, I am glad to see the roadmap up on-line but without a planning / milestones it is not yet clear what is going into the various components. I posted some specific comments in reply to Brad's post, here are some general comments on this roadmap (it is really missing the details and feels like a quick copy of the RFC to me): Core process engine using BPMN 2.0 =========================== Glad to see the common executable worked out in the roadmap, this is what we can expect. Should be in the first milestone. Would be nice to see the existing components listed that can be leveraged or merged for this functionality. Human tasks ========== Going to provide complete spec support in first milestone release along with human task web console supporting the task life cycle (claim, start, complete, etc.) and custom task forms? If not would be nice to see the work listed that needs to be done, leveraged from other implementation, etc. Eclipse-based tooling for creating BPMN2 processes ===================================== Seems this can be leveraged from the existing components? list them out maybe with the milestones that they will appear in. What about "basic validation, testing and debugging," this means? does this map to existing components? Web-based tooling for creating BPMN2 processes =================================== Here you map it to the existing implementation, great! Process repository ============== Can you expand on the components that already exist? What is here and not so that you can provide milestone dates for what will appear when? Pretty sure you are going to leverage the JCR stuff from Drools or extend this for process definition artefacts for example? Process management console ===================== A core component if we want to sell this thing! Details again, what it will do, what can be leveraged, what is to be done and milestones they will appear in. Reporting ======= Nice to have... Installation script (and demo setup) ========================= Leveraging the existing jBPM4 stuff? what are you going to target? community scripts are way too monolithic for customer usage if you ask me. Anyway, again a breakdown and planning would be nice. Documentation =========== Blank == nice to have? ;-) Migration ======= I think you need to take a look at API mapping too. Why not provide some api call mapping in the tooling where it is possible? I expect I would be able to provide customer input (code bases) for looking at real world implementations to start generating a matrix of used calls for example? Just migration of the jPDL 3/4 -> BPMN2.0 would be rather weak attempt. If it turns out that a customer uses API calls, no custom SQL or hibernate tweaking, plays nice in the infrastructure code they create, then it is conceivable that we could provide simple instance migration. (Cross your fingers!). I have a personal interest in this area and if we can go a bit farther in detailing the components and development that needs to be done in the roadmap, I will complete my blog articles on jBPM Migration Strategies (http://www.schabell.org/2010/03/jbpm-migration-strategies-introduction.html). Conclusions: ========= Basically I would like to discuss the details within each area to be developed for the roadmap; what is the break down of components to be developed, what is existing and/or ready to be leveraged, map this to the components, planning in milestones for what is to appear and when. With that kind of roadmap you can then leverage JIRA for the roadmap creating milestones for all to watch progress and/or help with by picking up work to be done. Looking forward to this, erics On Tue, May 25, 2010 at 5:06 PM, Kris Verlaenen <kverlaen(a)redhat.com&gt; wrote: