OpenRules just announced a new Long-Term-Support (LTS) Release 10.4.0 built in accordance with OpenRules Lifetime Release Policy. This policy puts you in control of your upgrade strategy by making it easier for you to plan and budget for OpenRules’ product upgrades.  Our Long-Term-Support releases are designed to be stable and reliable. They undergo extensive testing and are regularly updated with bug fixes to ensure they are optimized for use over an extended period of time. This stability is crucial for larger businesses and organizations that rely on OpenRules for their critical day-to-day operations. When it’s time to upgrade, as a licensed customer you’ll have rights to major product releases. Thus, you can benefit from OpenRules product stability and leadership in constantly improving decision intelligence technology.

Long-Term-Support (LTS). OpenRules designates certain releases as Long-Term-Support (LTS) releases after their essential real-world use in various production environments of OpenRules customers. The current LTS release is 10.4.0. OpenRules intends to make future LTS releases every 2 years. OpenRules non-LTS releases usually contain new capabilities and implementation enhancements of the most recent LTS release. We produces 3-4 non-LTS releases per year – see Release History. However, some customers prefer not to upgrade to non-LTS releases and stay with the latest LTS release. Once a new LTS release is made available, any previous non-LTS release is considered superseded. It allows you to enjoy continued peace of mind, knowing that we’ll always support your business. 

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.