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 [email protected] regards Mark On 26 Sep 2012, at 13:28, Chris Rankin <[email protected]> wrote: > Hi, > > I recently found and fixed a problem in drools-core-5.1.1 which was > preventing my project from working: > > https://issues.jboss.org/browse/JBRULES-3630 > > The fix has been accepted into the master branch and (allegedly) > released as 5.4.1.Final, but this is no good to me because my project > is still using Drools 5.1.1. And no, I'm not in a position to "just > upgrade" to 5.4.1. > > Can we merge the fix for JBRULES-3630 into the 5.1.1 branch and > release it as 5.1.2 please? > > Thank you, > Chris Rankin > _______________________________________________ > rules-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-dev _______________________________________________ rules-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-dev
