Release History

2024-current 
Release 11.1.0:  Sep-2025
Release 11.0.1:  July-2025
Release 10.5.0:  Feb-2025
Release 10.4.1:  Nov-2024 (LTS)
Release 10.4.0:  Aug-2024 (LTS) 
Release 10.3.0:  May-2024
Release 10.1.0:  Jan-2024
2022-2023 
Release 10.0.0:  July-2023
Release 9.1.1:  Apr-2023
Release 9.1.0:  Jan-2023
Release 9.0.0:  Nov-2022 
Release 8.5.3:  June-2022
Release 8.5.2:  June-2022
Release 8.5.1:  Apr-2022
Release 8.5.0:  Mar-2022
2020-2021 
Release 8.4.3:  Dec-2021
Release 8.4.2:  Nov-2021
Release 8.4.1:  Aug-2021
Release 8.4.0:  June-2021
Release 8.3.2:  Apr-2021
Release 8.3.1:  Mar-2021
Release 8.3.0:  Jan-2021 
Release 8.2.1:  Nov-2020
Release 8.2.0:  June-2020
Release 8.1.2:  May-2020
Release 8.1.1:  March-2020
Release 8.1.0:  Feb-2020 
2014-2019   
Release 8.0.2:  Oct-2019
Release 8.0.1:  Aug-2019 
Release 7.0.1:  May-2019
Release 7.0.0:  Aug-2018
Release 6.4.3:  Oct-2017
Release 6.4.2:  May-2017
Release 6.4.1:  Dec-2016
Release 6.4.0:  July-2016
Release 6.3.4:  Dec-2015
Release 6.3.3:  May-2015
Release 6.3.2:  Dec-2014
Release 6.3.1:  May-2014
Release 6.3.0:  Feb-2014
2012-2013 
Release 6.2.6:  Dec-2013
Release 6.2.5:  Aug-2013
Release 6.2.4:  May-2013
Release 6.2.3:  Jan-2013
Release 6.2.2:  Sep-2012
Release 6.2.1: June-2012
Release 6.2.0: Mar-2012 
2010-2011
Release 6.1.3: Dec-2011
Release 6.1.2: Sep-2011
Release 6.1.1: Aug-2011
Release 6.0.1: Mar-2011
Release 5.4.1: Oct-2010
Release 5.4.0: June-2010
Release 5.3.3: May-2010
2008-2009
Release 5.3.2: Oct-2009
Release 5.3.1: July-2009
Release 5.3.0: March-2009
Release 5.2.0: Jan-2009
Release 5.1.0:  Aug-2008
Release 5.0.2:  Apr-2008
Release 5.0.1:  Mar-2008
2005-2007
Release 4.1.0: Sep-2007
Release 4.0.0: Jul-2007
Release 3.0.0: Sep-2006
Release 2.3.0: Feb-2006
Release 2.2.1: Nov-2005
Release 2.2.0: Sep-2005
Release 2.1.0: May-2005
Release 2.0.0: Mar-2005                
2003-2004
Release 1.1.0:  Nov-2004
Release 1.0.2:  May-2004
Release 1.0.1:  Apr-2004
Release 1.0.0:  Dec-2003

Lifetime Release Policy. OpenRules maintains a Lifetime Release Policy that puts you in control of your upgrade strategy by making it easier for you to plan and budget for OpenRules product upgrades.

Release Preparation and Validation. We use an automated source code analysis tool SonarQube for automated source code analysis. It is integrated into our build pipeline with a Maven’s Sonar plugin. Every change in our codebase is subject to a peer review and our developers are trained to apply secure coding practices as outlined in the OWASP Secure Coding Guide.

To verify that our software adheres to industry standards for Systems/Software Development Lifecycle (SDLC) security, every build of the new release uses a special Maven plugin from NIST NVD, the official U.S. government repository. This plugin automatically validates all 3^rd party packages for security vulnerability forcing us to use only the latest secured versions.

We always review our applications for security vulnerabilities. We never build a new release without checking it for security vulnerabilities using the OWASP secure coding practices and NVD plugin.