<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">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 ... <br>
Not sure why jBPM Form Builder and Designer would need branching
and POMs updates? Can you please explain?<br>
<br>
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.<br>
<br>
Thanks a lot.<br>
Tihomir<br>
<br>
On 10/15/12 7:41 AM, Michael Anstis wrote:<br>
</div>
<blockquote
cite="mid:CAAG9P0tgFTwbyV54XP7CT6N5N=DMhKF+uoWbyeWGH0dj4Noxjg@mail.gmail.com"
type="cite">Hi,<br>
<br>
Just a note to you all to advise that the 5.5.x branches have been
made on github and Jenkins jobs setup accordingly.<br>
<br>
Should you make changes to master that are needed for 5.5.x please
be sure to cherry-pick...<br>
<br>
There are a couple of remaining tasks:-<br>
<ul>
<li>jBPM Form Builder - Needs branching and POM's updated.</li>
<li>jBPM Designer - Needs branching, POM's updated and Jenkins
job <a moz-do-not-send="true"
href="https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/Drools%20jBPM/job/guvnor-5.5.x/">https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/Drools%20jBPM/job/guvnor-5.5.x/</a>
updated to build jBPM Designer 5.5.x.</li>
<li>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.</li>
</ul>
The jBPM Team wanted to handle these changes for 5.5.0.Beta1 so I
have assumed the same for the branch.<br>
<br>
With kind regards,<br>
<br>
Mike<br>
</blockquote>
<br>
</body>
</html>