[rules-dev] Request for Community Release of drools-core-5.1.2 with fix from JBRULES-3630

[Chris Rankin]

So let's get this straight:
I find, debug *and* patch the problem for you, and then you expect me
to pay you to release it as well?

You. Are. Dreaming.

On Thu, Sep 27, 2012 at 9:35 PM, Mark Proctor <mproctor at codehaus.org> wrote:
> We don't' publish community patch releases for maintenance of older versions.
>
> 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:
> http://blog.athico.com/2011/04/drools-jbpm-community-versus-product.html
>
> If you would like a BRMS subscription, where a patched jar can be provided, please contact sales at jboss.com