drools 5.5, 6.0 and roadmap
Locked
drools 5.5, 6.0 and roadmap
 
|
http://blog.athico.com/2012/07/drools-55-60-and-future.html
--- copied from blog article ---
Some time soon we will branch master.
The current master will be branched to 5.5 and then master will
become 6.0.
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. I hope we can release a 5.5 within the next 4-5 months; this may very depending on the impact of other commitments. 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. 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. 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.
General rule syntax
The event sequencing draft can be found
here:
The functional programming aspects are
still being explored on this wiki page:
We will eventually roll the later two back in the Drools60
document, to provide a single document that covers the 6.0
language specific.
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.
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).
Here goes nothing!!!
Mark
_______________________________________________ rules-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/rules-dev |
Re: drools 5.5, 6.0 and roadmap
|
|
5.5 will remain JDK5 complaint. 6.0
will move to JDK6.
We will provide migration scripts from 5.x. Mark On 04/07/2012 04:32, Mark Proctor wrote: http://blog.athico.com/2012/07/drools-55-60-and-future.html _______________________________________________ rules-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/rules-dev |
Administrator
|
We will develop 5.5 and 6.0 in parallel.This covers drools expert. Does it cover guvnor? Given the list of repository, which get branched between 5.5 and 6.0 early on? droolsjbpm-knowledge: yes? drools: yes jbpm: no? droolsjbpm-integration: only possible if jbpm is also branched guvnor: no? Branching would not be practical (too much cherry picking). droolsjbpm-tools: only possible if guvnor is also branched drools-planner: no. Planner will work solely on the knowledge-api and therefor need no branching process-designer: no At some point, all these repo's will be branched between 5.5 and 6.0 (although jbpm and designer might have a different branch name), but the question is which repo's will truly develop 5.5 and 6.0 in parallel. Op 04-07-12 05:59, Mark Proctor schreef:
-- With kind regards, Geoffrey De Smet _______________________________________________ rules-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/rules-dev |
|
I would love to see that happening for jbpm as well.Â
5.4 and 6 in parallel
On Wed, Jul 4, 2012 at 4:25 AM, Geoffrey De Smet <[hidden email]> wrote:
 - MyJourney @ http://salaboy.wordpress.com  - Co-Founder @ http://www.jugargentina.org  - Co-Founder @ http://www.jbug.com.ar   - Salatino "Salaboy" Mauricio - _______________________________________________ rules-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/rules-dev |
|
In reply to this post by Mark Proctor
I've sprinkled this
https://community.jboss.org/wiki/Drools60 liberally with comments. Several of them are pointing out what I think is an error I can't correct, or points that need clarification to be understandable in the first place. On 04/07/2012, Mark Proctor <[hidden email]> wrote: > 5.5 will remain JDK5 complaint. 6.0 will move to JDK6. So why not JDK7 right away? They are already talking about JDK8... -W _______________________________________________ rules-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/rules-dev |
|
|
All of my comments are tagged with "WL".
On 04/07/2012, Wolfgang Laun <[hidden email]> wrote: > I've sprinkled this > https://community.jboss.org/wiki/Drools60 > liberally with comments. Several of them are pointing out what I think > is an error I can't correct, or points that need clarification to be > understandable in the first place. _______________________________________________ rules-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/rules-dev |
Re: drools 5.5, 6.0 and roadmap
|
|
On 04/07/2012 09:54, Wolfgang Laun
wrote:
All of my comments are tagged with "WL". On 04/07/2012, Wolfgang Laun [hidden email] wrote:I've sprinkled this https://community.jboss.org/wiki/Drools60 liberally with comments. Several of them are pointing out what I think is an error I can't correct, or points that need clarification to be understandable in the first place. Replied, have left your/mine comments
there even after correction. So that you can read an remove both if
satisfied.
_______________________________________________ rules-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/rules-dev _______________________________________________ rules-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/rules-dev |
|
|
Re-edited. - Some WLs are still there, one or two might be new or
substantially changed. In a couple of places I was persistent enough to dig myself in. Now I'm going to write something that has a personal undertone, so brace yourself. You know, from previous clashes, that ultimately I mean well and try to be careful not to hurt people's feelings - at least not more than necessary ;-) I feel at liberty to write what I'm going to write because the premise is something I've heard you confess yourself: That you don't like to, and have problems with, writing English texts. Now I *suspect* (!) that this trait also has an impact on your ardour or agility as a programming language designer. Harshly said, some of the constructs you propose read as awkwardly as some of the sentences one can find in documentation written by you. OK, so I've said it. Perhaps you think about it, and please, please, don't be cross with me. After all, it's only Drools I'm caring for ;-) -W _______________________________________________ rules-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/rules-dev |
Re: drools 5.5, 6.0 and roadmap
|
|
It's early days, it will take time to refine. Once we start implementing
this in the parser, we will find aspects that will not work, due to ambiguity; so stuff will come out of the wood work. Even after implementation we'll have plenty of time to tweak it, until we start using it in ernest, it's hard to get a real feel for things. Btw I'm not sure what you mean by "alternatives" here, I suspect that will confuse others too: The 'case' phrases are not alternatives, but 'break' is available to terminate the switch CE after a match Also maybe re-include my rich/poor example, it'll help illustrate the usage. But can remove my MDP bit, so it's just another part of the documentation. Mark On 04/07/2012 14:57, Wolfgang Laun wrote: > Re-edited. - Some WLs are still there, one or two might be new or > substantially changed. In a couple of places I was persistent enough > to dig myself in. > > > Now I'm going to write something that has a personal undertone, so > brace yourself. You know, from previous clashes, that ultimately I > mean well and try to be careful not to hurt people's feelings - at > least not more than necessary ;-) > > I feel at liberty to write what I'm going to write because the premise > is something I've heard you confess yourself: That you don't like to, > and have problems with, writing English texts. > > Now I *suspect* (!) that this trait also has an impact on your ardour > or agility as a programming language designer. Harshly said, some of > the constructs you propose read as awkwardly as some of the sentences > one can find in documentation written by you. > > OK, so I've said it. Perhaps you think about it, and please, please, > don't be cross with me. After all, it's only Drools I'm caring for ;-) > > -W > _______________________________________________ > rules-dev mailing list > [hidden email] > https://lists.jboss.org/mailman/listinfo/rules-dev _______________________________________________ rules-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/rules-dev |
|
|
On 4 July 2012 16:15, Mark Proctor <[hidden email]> wrote:
I was trying to say that 'switch' doesn't select at most one of its 'case' phrases unless you use 'break'. Matching more than one 'case' is possible, resulting in multiple activations, similar to 'or'. I'll clarify. -W _______________________________________________ rules-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/rules-dev |
English as a 2nd Language
|
Greegings:
Here I am returning to Drools list again as an interloper. I think perhaps that we should all revisit "My Fair Lady" [based on "Pygmalion"] and the very first so-called song, "Why Can't the English Teach Their Children How to Speak?" as spoken-sung by Rex Harrison (the Professor Dolittle character). You see, even the English themselves very rarely know the proper English constructs of their own language, especially when spoken, and even when written they seem to leave dangling prepositions and intransitive verbs, such as "to" or "from", at the end of a sentence. It virtually makes ones skin crawl at times. Here in the colonies even the national news casters make the most appaling mistakes. It's no wonder that the children in either country can make themselves understood these days without making a mistake in a single spoken sentence. Here in the Southern and Texan climes, "can't" often rhymes with paint and ain't, "get" rhymes with hit and, most dredfull of all, we most often hear, "Where are you going to?" quite often. The other phrase in the South is, "What are you fixing to do?" meaning, "What you about to do?" Only in the South... So, even though you find many mistakes in the English language in Drools code and documentation, bear with it. It is NOT as bad as it appears and, if you can understand the overall meaning and if the general intent is clear, leave it alone and let it ride. Correct it only if the meaning is not clearly understood or if the meaning is muddled and not clear to the ordinary mortal, such as the beginner or the intermediate programmer. -- SDG jco _______________________________________________ rules-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/rules-dev |
Re: drools 5.5, 6.0 and roadmap
|
|
In reply to this post by laune
On 04/07/2012 15:54, Wolfgang Laun
wrote:
Agreed maybe "match" would be a better word. It is in the spirit of pattern matching in erlang and scala. Mark
_______________________________________________ rules-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/rules-dev |
«
Return to Drools: Developer (committer) mailing list
|
1 view|%1 views
Loading...
| Powered by Nabble | Edit this page |