This is how I see the 4.2 roadmap (main "big ticket" features) - I think this is realistic for a short schedule (and I am probably missing things, but lets keep it realistic): (FYI this is only what *I* know is going on) of course critical fixes will take priority, and there are many other small tasks that will make it in as well - I am just trying to avoid a bloat that means 4.2 is 5 ;) BRMS/Tooling: * Role/capability based security (using seam security) in the BRMS * GUI for analysis tool/QA reporting on package quality (based on contributions from Toni Rikkola) * Declarative testing tools in BRMS (web GUI) - junit extension for unit testing single rules * IDE GUI to build/deploy a package * Ruleflow stuff (Kris??) * Web Service deployment of "decision services" Core/lang: * Improved error messages (relies on bug reports/examples) * pluggable extractors (for future ontology) UNKNOWN: * IDE/BRMS integration * Data driven "enums" in BRMS (this probably has to wait for a fuller ontology I am afraid - else it is a can of worms - can hack something)

we are doing a quick release for 4.2 before xmas. CEP/ESP won't be ready for then, but you can still work on it in a branch for 5.0. Mark Edson Tirelli wrote: I think we need to define what would be the desirable timeframe of the next release?! I would really like to include the initial CEP/ESP support in that release. There are also a few feature requests in JIRA regarding things like multi-pattern accumulate, etc. []s Edson 2007/8/14, Michael Neale <michael.neale(a)gmail.com&gt;: > > This is how I see the 4.2 roadmap (main "big ticket" features) - I think > this is realistic for a short schedule (and I am probably missing things, > but lets keep it realistic): > (FYI this is only what *I* know is going on) > of course critical fixes will take priority, and there are many other > small tasks that will make it in as well - I am just trying to avoid a bloat > that means 4.2 is 5 ;) > > BRMS/Tooling: > * Role/capability based security (using seam security) in the BRMS > * GUI for analysis tool/QA reporting on package quality (based on > contributions from Toni Rikkola) > * Declarative testing tools in BRMS (web GUI) > - junit extension for unit testing single rules > * IDE GUI to build/deploy a package > * Ruleflow stuff (Kris??) > * Web Service deployment of "decision services" > > > Core/lang: > * Improved error messages (relies on bug reports/examples) > * pluggable extractors (for future ontology) > > > UNKNOWN: > * IDE/BRMS integration > * Data driven "enums" in BRMS (this probably has to wait for a fuller > ontology I am afraid - else it is a can of worms - can hack something) > > -- Edson Tirelli Software Engineer - JBoss Rules Core Developer Office: +55 11 3529-6000 Mobile: +55 11 9287-5646 JBoss, a division of Red Hat @ www.jboss.com ------------------------------ _______________________________________________ rules-dev mailing list rules-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/rules-dev