<p>If you have a patch, apply it locally and be done with. Community drives the current not the past. I am sure will can apply your patch to 5.5.0.Beta2.</p>
<p>sent on the move</p>
<p>On 27 Sep 2012 23:25, "Chris Rankin" <<a href="mailto:rankincj@googlemail.com">rankincj@googlemail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So let's get this straight:<br>
I find, debug *and* patch the problem for you, and then you expect me<br>
to pay you to release it as well?<br>
<br>
You. Are. Dreaming.<br>
<br>
On Thu, Sep 27, 2012 at 9:35 PM, Mark Proctor <<a href="mailto:mproctor@codehaus.org">mproctor@codehaus.org</a>> wrote:<br>
> We don't' publish community patch releases for maintenance of older versions.<br>
><br>
> The cost is simply too high, as releasing can take several days and must be tested. More importantly this is how Red Hat provides value to our paying subscription customers - where we provide 5 years of patch releases, without features. See this blog for more information:<br>
> <a href="http://blog.athico.com/2011/04/drools-jbpm-community-versus-product.html" target="_blank">http://blog.athico.com/2011/04/drools-jbpm-community-versus-product.html</a><br>
><br>
> If you would like a BRMS subscription, where a patched jar can be provided, please contact <a href="mailto:sales@jboss.com">sales@jboss.com</a><br>
<br>
_______________________________________________<br>
rules-dev mailing list<br>
<a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
</blockquote></p>