Thomas,
Thanks for the summary... It's kind of what I grasped from all separate things going on. Others not so close to the project might get a wrong idea... dead links, out of date docs etc...
Maybe this summary should be a sticky post in both forums with links to (wiki) pages where more info can be found. It'll cost me less time to keep 'the community' lined up....
Besides this, I agree that the new infrastructure is superiour and is a good move... (new forums also? pleeeeaaassseeee ;-) )
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162754#4162754
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162754
Hi Alejandro,
I'm not quite clear about the situation and direction for BPEL. I guess
that the BPEL component should still be included in the upcoming jPDL
releases, right?
For that it need to be made available in the maven repository and
integrated in the IzPack installer - I can help you with both.
This is covered by
http://jira.jboss.org/jira/browse/JBPM-1354
The following applies to BPEL in the same way as for GPD
Looking at the BPEL roadmap
http://jira.jboss.org/jira/browse/BPEL?report=com.atlassian.jira.plugin.s...
It seems that it is undefined when a certain release is to be expected
and how it relates to the overall jbpm release cycle.
I therefore suggest, we align the BPEL roadmap with rest of deliverables
in a similar way we do as for jBPM4
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=138255
Could you please create the respective versions in JIRA and assign
release dates to them?
The next two releases should come out on
1-Sep-2008
1-Nov-2008
This move is motivated by the need to improve predictability for BPM
related releases. It should not affect the amount of stuff that gets done.
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Ronald,
we are in the process of major clean up and restructuring. Areas that are effected are:
* usage of mailing lists
* wiki documentation
* source repository
* build process
* automated test coverage
* release procedure
* API design
If you look at these areas on-by-one, you sure realize that there is much needed work to be done. Due to the open nature of our development process it unavoidable (and even desired) that the community sees snapshots of the work in progress.
We have be no means completed that restructuring yet - please stay with us through this part of a bumpy road - you can take my word that by the end of this year, you will find an infrastructure that is far superior to what is there currently and much more enjoyable to work with for everybody.
cheers
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162712#4162712
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162712