yeah I think it should be even shorter if possible. <br><br>My big ticket items are testing and analysis, I doubt I will have time for much else.<br><br><div><span class="gmail_quote">On 8/15/07, <b class="gmail_sendername">
Mark Proctor</b> <<a href="mailto:mproctor@codehaus.org">mproctor@codehaus.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
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.<br>
<br>
Mark<br>
Edson Tirelli wrote:
<blockquote type="cite"><div><span class="e" id="q_11464c442e8a0ccf_1"><br>
I think we need to define what would be the desirable timeframe of
the next release?! <br>
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.
<br>
<br>
[]s<br>
Edson<br>
<br>
<br>
<div><span class="gmail_quote">2007/8/14, Michael Neale <<a href="mailto:michael.neale@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">michael.neale@gmail.com</a>>:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">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>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
Edson Tirelli<br>
Software Engineer - JBoss Rules Core Developer<br>
Office: +55 11 3529-6000<br>
Mobile: +55 11 9287-5646<br>
JBoss, a division of Red Hat @ <a href="http://www.jboss.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
www.jboss.com</a>
</span></div><pre><hr size="4" width="90%">
_______________________________________________<br>rules-dev mailing list<br><a href="mailto:rules-dev@lists.jboss.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">rules-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">https://lists.jboss.org/mailman/listinfo/rules-dev</a>
</pre>
</blockquote>
<br>
</div>
</blockquote></div><br>