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):<br>(FYI this is only what *I* know is going on)
<br>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 ;)<br><br>BRMS/Tooling:<br>* Role/capability based security (using seam security) in the BRMS
<br>* GUI for analysis tool/QA reporting on package quality (based on contributions from Toni Rikkola)<br>* Declarative testing tools in BRMS (web GUI)<br> - junit extension for unit testing single rules<br>* IDE GUI to build/deploy a package
<br>* Ruleflow stuff (Kris??)<br>* Web Service deployment of "decision services"<br><br><br>Core/lang:<br>* Improved error messages (relies on bug reports/examples)<br>* pluggable extractors (for future ontology)
<br><br><br>UNKNOWN: <br>* IDE/BRMS integration<br>* 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)<br><br>