Hi Tiho,
I saw Kris had changed jBPM's POMs to 5.5.0-SNAPSHOT and Marco confirmed
jBPM has moved to 5.5.x (and not 5.4.x as we had with Beta1) this morning.
I am therefore (led to believe) 5.5.x is correct for jBPM.
Since jBPM has been branched to 5.5.x I'd assume Designer and Form Builder
had to branch too. Of course I could be mistaken, IDK your projects as well
as you do.
Mark sent an email over the weekend saying we were to start on CR1 this
week.
With kind regards,
Mike
On 15 October 2012 12:55, Tihomir Surdilovic <tsurdilo(a)redhat.com> wrote:
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/g...
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