I would love to see that happening for jbpm as well. <div>5.4 and 6 in parallel<br><br><div class="gmail_quote">On Wed, Jul 4, 2012 at 4:25 AM, Geoffrey De Smet <span dir="ltr"><<a href="mailto:ge0ffrey.spam@gmail.com" target="_blank">ge0ffrey.spam@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div text="#000000" bgcolor="#ffffff">
<br>
<blockquote type="cite">We will develop 5.5 and 6.0 in parallel. </blockquote>
This covers drools expert. Does it cover guvnor?<br>
<br>
<br>
Given the list of repository, which get branched between 5.5 and 6.0
<i>early on</i>?<br>
<br>
droolsjbpm-knowledge: yes?<br>
drools: yes<br>
jbpm: no?<br>
droolsjbpm-integration: only possible if jbpm is also branched<br>
guvnor: no? Branching would not be practical (too much cherry
picking).<br>
droolsjbpm-tools: only possible if guvnor is also branched<br>
drools-planner: no. Planner will work solely on the knowledge-api
and therefor need no branching<br>
process-designer: no<br>
<br>
At some point, all these repo's will be branched between 5.5 and 6.0<br>
(although jbpm and designer might have a different branch name),<br>
but the question is which repo's will truly develop 5.5 and 6.0 in
parallel.<br>
<br>
Op 04-07-12 05:59, Mark Proctor schreef:
<blockquote type="cite">
<div>5.5 will remain JDK5 complaint. 6.0
will move to JDK6.<br>
<br>
We will provide migration scripts from 5.x.<br>
<br>
Mark<br>
On 04/07/2012 04:32, Mark Proctor wrote:<br>
</div>
<blockquote type="cite">
<a href="http://blog.athico.com/2012/07/drools-55-60-and-future.html" target="_blank">http://blog.athico.com/2012/07/drools-55-60-and-future.html</a><br>
--- copied from blog article ---<br>
<div style="margin-bottom:0cm"> Some time soon we will branch
master. The current master will be branched to 5.5 and then
master will become 6.0.<br>
<br>
We will develop 5.5 and 6.0 in parallel. In general we will
try to apply as many bug fixes and stable features to both
branches, for as long as it's practically possible. At some
point 6.0 will diverge too much and the cost will become too
high.<br>
<br>
I hope we can release a 5.5 within the next 4-5 months; this
may very depending on the impact of other commitments.<br>
<br>
6.0 will be a longer term effort, and will involve the most
drastic changes at both the engine and language level to date.
The engine algorithm will be almost completely new, and will
no longer be considered a Rete implementation. Instead it will
be a lazy collection oriented matching algorithm, that will
support adaptive network topologies. First we'll deliver the
lazy matching algorithm and then shift to collection oriented.
The adaptive network topologies will take more time and may
deliver after 6.0. These engine changes will lay the ground
work for exploiting multi-cpu architectures, and durable
backing stores (Active Databases). I also hope we can
integrate our engine with a tableaux algorithm, to provide
seamless description logic capabilities for semantic
ontologies; but that's still a very open research area, with
many unknowns.<br>
<br>
6.0 will most likely retain api comparability (no current
plans to break it), however the DRL syntax will be broken. DRL
has been backwards compatible, excluding bugs and regressions,
for almost 7 years now. We plan to take this opportunity to
revamp DRL, as we fully embrace becoming a hybrid reasoning
engine. We will fully explore passive, reactive, relational
and functional programming styles. The hope is we can create a
declarative language system, more flexible and more suitable
for a wider range of solutions. I also really want to address
some of the usability problems associated with rule execution
control, particularly around salience and the various rule
groups (agenda-groups, ruleflow-groups, activation-groups).
Relative salience and a single concept around a flexible
RuleModule will hopefully make this possible. We have to start
making things easier, simpler and more consistent.<br>
<br>
We are just starting to flesh out our designs, figuring out
what works and what doesn't. All are at the very early stages,
much has not yet been added, and everything is open to debate.</div>
<div style="margin-bottom:0cm"> <br>
</div>
<div style="margin-bottom:0cm"> General rule syntax</div>
<div style="margin-bottom:0cm"> <a href="https://community.jboss.org/wiki/Drools60" target="_blank">https://community.jboss.org/wiki/Drools60</a></div>
<div style="margin-bottom:0cm"> <br>
</div>
<div style="margin-bottom:0cm"> The event sequencing draft can
be found here:</div>
<div style="margin-bottom:0cm"> <a href="https://community.jboss.org/wiki/EventSequencing" target="_blank">https://community.jboss.org/wiki/EventSequencing</a><br>
<br>
</div>
<div style="margin-bottom:0cm"> The functional programming
aspects are still being explored on this wiki page:</div>
<div style="margin-bottom:0cm"> <a href="https://community.jboss.org/wiki/FunctionalProgrammingInDrools" target="_blank">https://community.jboss.org/wiki/FunctionalProgrammingInDrools</a></div>
<div style="margin-bottom:0cm"> <br>
</div>
<div style="margin-bottom:0cm"> We will eventually roll the
later two back in the Drools60 document, to provide a single
document that covers the 6.0 language specific.</div>
<div style="margin-bottom:0cm"> <br>
</div>
<div style="margin-bottom:0cm"> The web based tooling is also
under going a revamp. It will offer a more flexible workbench
like experience where all panels are plugins, with support for
perspectives. This will allow us to build a consistent and
unified approach to our web tooling efforts across
Drools&jBPM. We also have a mechanism now that will allow
our web based components, such as decision tables and guided
editors to be used in Eclipse – to create a consistent
experience between the two environments. We have back ported
the java7 vfs api and have a Git implementation for this, we
will also continue provide a JCR implementation. So far Git is
looking extremely scalable and easy to use. JGit provides a
full java implementation, making out of the box use easy. Stay
tuned for more news. Hopefully in less then 2 months we will
have some early proof of concepts to show, for the web based
efforts.</div>
<div style="margin-bottom:0cm"> <br>
</div>
<div style="margin-bottom:0cm"> If you want to help make
history happen, joins us on irc (real time chat). You can also
leave comments on the wiki pages or the mailing lists
(developer list).</div>
<div style="margin-bottom:0cm"> <a href="http://www.jboss.org/drools/irc" target="_blank">http://www.jboss.org/drools/irc</a></div>
<div style="margin-bottom:0cm"> <a href="http://www.jboss.org/drools/lists" target="_blank">http://www.jboss.org/drools/lists</a></div>
<div style="margin-bottom:0cm"> <br>
</div>
<div style="margin-bottom:0cm"> Here goes nothing!!! </div>
<div style="margin-bottom:0cm"> <br>
</div>
<div style="margin-bottom:0cm"> Mark</div>
<br>
</blockquote>
<br>
<br>
<pre><fieldset></fieldset>
_______________________________________________
rules-dev mailing list
<a href="mailto:rules-dev@lists.jboss.org" target="_blank">rules-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><span class="HOEnZb"><font color="#888888">
</font></span></pre><span class="HOEnZb"><font color="#888888">
</font></span></blockquote><span class="HOEnZb"><font color="#888888">
<br>
<pre cols="72">--
With kind regards,
Geoffrey De Smet</pre>
</font></span></div>
<br>_______________________________________________<br>
rules-dev mailing list<br>
<a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br> - MyJourney @ <a href="http://salaboy.wordpress.com" target="_blank">http://salaboy.wordpress.com</a><div> - Co-Founder @ <a href="http://www.jugargentina.org" target="_blank">http://www.jugargentina.org</a><br>
- Co-Founder @ <a href="http://www.jbug.com.ar" target="_blank">http://www.jbug.com.ar</a><br> <br> - Salatino "Salaboy" Mauricio -</div><br>
</div>