September 2008 - jbpm-dev - Jboss List Archives

JIRA Freeze 29-Nov-2008

by Thomas Diesler

Hi Folks, please find attached the current snapshot of unresolved issues for the next release cycle Jira Freeze: Mon,29-Sep-2008 Code Freeze: Mon,27-Oct-2008 Relesae: Sat,01-Nov-2008 Please review your issues and comment appropriately. Next Monday we should have a list that everybody has agree with. cheers -thomas -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler BPM Product Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

17 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: community branch

by jbarrez

I also believe this is a good idea. Just make sure that the community version does not get better than the official one ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179002#4179002 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179002

17 years

1
0
0 / 0

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

by thomas.diesler＠jboss.com

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 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 sak him to work with you to get it resolved. cheers View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179001#4179001 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179001

17 years

1
0
0 / 0

[Design of JBoss jBPM] - community branch

by tom.baeyens＠jboss.com

when jbpm 4 goes GA, i think we should do similar as the SEAM guys: create a community branch. that allows for an easy of contributing and we can then look if features get completed (with test cases and docs). we can decide to lend a hand if we want but that should not be treated as a given. as long as the feature is not accepted by the team, it only stays in the community branch and doesn't make it into the next GA release. It's probably too early to think about this but i wanted to share this thought as i just saw the seam community branch and i think it is a good idea. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179000#4179000 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179000

17 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: Pass process instance key to sub process

by jbarrez

Tom, that is a very good idea! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178999#4178999 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178999

17 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: Pass process instance key to sub process

by tom.baeyens＠jboss.com

this is a good addition. but keep in mind that just posting the code is not enough. also the XSD need to be updated, test cases need to be created for each feature and the documentation needs to be updated. keep that in mind as we will not be able to do that work for this contribution. without those additional elements we cannot add it to the codebase. i just saw that SEAM has a community branch. maybe we should do something similar. a branch where community people can commit all kinds of stuff. then if it is considered ready, it can be merged into trunk. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178996#4178996 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178996

17 years

1
0
0 / 0

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

by kukeltje

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) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178993#4178993 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178993

17 years

1
0
0 / 0

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

by thomas.diesler＠jboss.com

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=hi... 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

17 years

1
0
0 / 0

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

by jbarrez

Ambitious writing! I'm looking forward to 1 november! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178985#4178985 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178985

17 years

1
0
0 / 0

[Design of JBoss jBPM] - jBPM project structure and direction

by thomas.diesler＠jboss.com

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 | 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=JBPM3SupportedTargetConta... * Defined set of target databases http://jbpm.dyndns.org/jbpmwiki/index.php?title=JBPM3SupportedTargetDatab... * 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 that, as I mentioned above already, 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/job/jBPM-Matrix 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 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178982#4178982 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178982

17 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jbpm-dev September 2008