9 Replies Latest reply on Sep 26, 2008 9:53 AM by kukeltje

jBPM project structure and direction

thomas.diesler Sep 26, 2008 4:00 AM

Folks,

as you might know already, we wanted to give the jBPM project a more professional infrastructure that allows us to work more effectively and regularly produce the quality releases that you would expect from a jboss project. Generally, as with all other jboss projects the formula holds

 project == product

This has been done now.

Currently we have two branches of the jBPM project

jBPM3: http://anonsvn.jboss.org/repos/jbpm/jbpm3
jBPM4: http://anonsvn.jboss.org/repos/jbpm/jbpm4

jBPM3 is the codebase that is currently in production and will be maintained for the lifetime of these production releases (i.e. 5 years).
The next jBPM3 release, which is jbpm-3.3.0 will come out 1-Nov-2008 and will improve on productization aspects

* SVN code repository
* Maven build system
* Automated Hudson QA http://jbpm.dyndns.org:8280/hudson/job/jBPM-Matrix
* Defined set of target containers http://jbpm.dyndns.org/jbpmwiki/index.php?title=JBPM3SupportedTargetContainers
* Defined set of target databases http://jbpm.dyndns.org/jbpmwiki/index.php?title=JBPM3SupportedTargetDatabases
* Defined set of supported JDK's (see Hudson Matrix)
* IzPack based installer http://jbpm.dyndns.org/jbpmwiki/index.php?title=JBPM3BuildingTheInstaller

In jBPM4 we removed the notion of separate jPDL, PVM projects. It is all jBPM4 now. The next jBPM4 release, which is jbpm-4.0.0-Alpha1 will also come out 1-Nov-2008 and is about setting up the project infrastructure such that (as I mentioned above already) it will allow us to work effectively. You will also have

* SVN code repository
* Maven build system
* Automated Hudson QA http://jbpm.dyndns.org:8180/hudson

Additionally to that we are going to start an API+CTS effort, that will introduce a stable public API that jBPM clients can interact with. Maybe not so obvious clients are ESB, Management Console, BI/BAM, Test Environments, Graphical designer, etc. Every concept that we introduce in the API will be verified in a compatibility test suite (CTS). Starting in November, you should see regular design discussions about the API in this forum.

Following on from the 1-Nov release you should expect to see regular jBPM releases every 8 weeks.

cheers

1. Re: jBPM project structure and direction

jbarrez Sep 26, 2008 4:08 AM (in response to thomas.diesler)

Ambitious writing! I'm looking forward to 1 november!
Actions
2. Re: jBPM project structure and direction

thomas.diesler Sep 26, 2008 4:20 AM (in response to thomas.diesler)

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 are for QA and documentation.

In JIRA you should see reliable release dates associated with any given version. Details of what remains to do be done is on the JIRA road map.

e.g. 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" ;-)
Actions
3. Re: jBPM project structure and direction

kukeltje Sep 26, 2008 4:34 AM (in response to thomas.diesler)

Thomas,

Kudos for al the great work. We've certainly come a long way which is largly because of your behind the scenes work. Although behind the scenes... I remeber you migrating cvs to svn while attending presentations in Dublin. The 'notebook' was for a brief period of time a 'laptop' again :-)

I still think that we ar not completely there yet.

There are multiple broken links in the jBPM site, among which are:
- the wiki link on the jpdl subproject site is incorrect
- the svn link on the pvm sources page is invalid
- the jira link on the pvm page is invalid
- the about jBPM link in the new wiki is invalid
- in two places there are links/references to http://www.jboss.org/jbossjbpm/jbpm_demo/ which does not exist
- the reference to the jBPM BPEL wiki from the jBPM BPEL pages leads to a non-existent page (http://wiki.jboss.org/wiki/JbpmBpel)
- the jBPM BPEL sources page does not contain the correct information

I a generic 'update' the site issue in jira and assigned it to 3.3.0 GA (might not be according the freeze 'rules', but I think it is needed and does not conflict with anything)
Actions
4. Re: jBPM project structure and direction

thomas.diesler Sep 26, 2008 4:51 AM (in response to thomas.diesler)

Thanks Ronald for your feedback.

Could you please work with somebody who has access to these resources to get the individual issues resolved. Unfortunately, not for every item above I know what you are talking about. Maybe Tom is you best contact - he should have all the access required.

I'll assign this issues

https://jira.jboss.org/jira/browse/JBPM-1760

to him and ask him to work with you to get it resolved.

cheers
Actions
5. Re: jBPM project structure and direction

kukeltje Sep 26, 2008 5:20 AM (in response to thomas.diesler)

Thanks, I will. And sorry for not posting a link to the Jira issue, I just forgot.
Actions
6. Re: jBPM project structure and direction

kukeltje Sep 26, 2008 7:38 AM (in response to thomas.diesler)

Oh and btw, are the Bull folks updated the pvm is now part of jBPM4? I remember and earlier discussion when that was the idea to and they were not to happy with it. Being dependent on the PVM ok, on jBPM??? hmmm...
Actions
7. Re: jBPM project structure and direction

kukeltje Sep 26, 2008 7:48 AM (in response to thomas.diesler)

Another thing would be to add the database versions to the Supported database versions
Actions
8. Re: jBPM project structure and direction

thomas.diesler Sep 26, 2008 9:03 AM (in response to thomas.diesler)

Yes, and in the spirit of open source you can follow Adding a Database Axis in case you want to lend a hand.
Actions
9. Re: jBPM project structure and direction

kukeltje Sep 26, 2008 9:53 AM (in response to thomas.diesler)

I'd love to, but aren't these the 'officially tested by JBoss internally' databases? This page is one the pages I'm not sure whether they *should* be changed by just anyone (not that I am just anyone ;-))

Besides that I already created a wiki account for the new wiki this morning
Actions

Go to original post