<p>I believe early next week, unless something critical arises. Mark Proctor will have the final say.</p>
<p>sent on the move</p>
<p>On 30 Sep 2011 18:55, "Jamie" <<a href="mailto:jshaw@llbean.com">jshaw@llbean.com</a>> wrote:<br type="attribution">> I recently ran into this issue and I've confirmed through testing that Drools<br>
> 5.3.0.CR1 in conjunction with JBPM 5.1.1 Final fixes the problem.<br>> <br>> We're currently rolling our JVMs nightly to prevent out of memory errors, so<br>> I need to deploy this upgrade to production ASAP. Can anyone tell me what<br>
> the target is for the final Drools 5.3.0 release?<br>> <br>> --<br>> View this message in context: <a href="http://drools.46999.n3.nabble.com/rules-users-Memory-leak-in-5-2-5-3-tp3280351p3383181.html">http://drools.46999.n3.nabble.com/rules-users-Memory-leak-in-5-2-5-3-tp3280351p3383181.html</a><br>
> Sent from the Drools: User forum mailing list archive at Nabble.com.<br>> _______________________________________________<br>> rules-users mailing list<br>> <a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users</a><br></p>