We are releasing jBPM version 5.4 and not 5.5. Typically we would create
the 5.5.x branch in jBPM after the 5.4.x release ...
Not sure why jBPM Form Builder and Designer would need branching and
POMs updates? Can you please explain?
Overall it would be really nice if we could coordinate branch creation
and releases (betas, crs, etc) in the cases where we are releasing
Drools and jBPM together. We were not able to advertize jBPM Beta1 due
to this.
Thanks a lot.
Tihomir
On 10/15/12 7:41 AM, Michael Anstis wrote:
Hi,
Just a note to you all to advise that the 5.5.x branches have been
made on github and Jenkins jobs setup accordingly.
Should you make changes to master that are needed for 5.5.x please be
sure to cherry-pick...
There are a couple of remaining tasks:-
* jBPM Form Builder - Needs branching and POM's updated.
* jBPM Designer - Needs branching, POM's updated and Jenkins job
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/Drools%20jBPM/job/guvnor-5.5.x/
updated to build jBPM Designer 5.5.x.
* jBPM contains properties overriding the Drools version in
droolsjbpm-parent POM. I suspect these need changing in master to
point to 6.0.0-SNAPSHOT.
The jBPM Team wanted to handle these changes for 5.5.0.Beta1 so I have
assumed the same for the branch.
With kind regards,
Mike
_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
