Version Support Policy

At Corner Bowl Software, we recognize that you need stability from Corner Bowl Server Manager. Stability ensures server management, server monitoring, compliance controls and audit reports don't become unusable. Stability is essential for Corner Bowl Server Manager's success as an enterprise network management, monitoring, compliance and auditing software tool.

We understand the importance of evolving with our customers' needs. The network management and monitoring landscape is constantly changing, and staying ahead means listening to our users. We're committed to regular updates and integrating new features that our customers request. This approach ensures our software not only meets today's challenges but also anticipates the needs of tomorrow's network environments. It's our mission to deliver a solution that's as dynamic and innovative as the networks it manages.

Product Versioning

The Corner Bowl Server Manager versioning format consists of four parts, often referred to as major.minor.build.revision. The addition of all four numbers is the full build number, for example 23.0.0.473. This format is used to specify the version of the installers and other binary files including executables and DLLs. Each part represents:

Release Frequency

We work toward a regular schedule of releases, so that you can plan and coordinate your updates with the continuing evolution of Corner Bowl Server Manager.

In general, expect the following release cycle:

• A major release every 2 years.
• A new revision release, or build, once a week.

This cadence of releases and builds is the result of customer driven feature requests as well as the rapidly changing network, server and compliance environment which Corner Bowl Server Manager is typically deployed.

Corner Bowl Software adheres to a strict code check-in policy for feature releases to maintain code integrity and quality. This policy mandates all code be peer-reviewed before merging, ensuring adherence to coding standards and detecting potential issues early. Developers write comprehensive unit tests for their code, achieving a predetermined level of code coverage. Continuous integration (CI) systems are employed to automate testing and build processes, verifying that the code integrates seamlessly with the existing codebase. Additionally, developers regularly sync their branches with the main branch to minimize merge conflicts. Finally, detailed commit messages that clearly describe each change and their impact on the project are required during each code check-in.

Support Window

All major releases are typically supported for 3 years.

Version Timelines

Current Downloads

To view release notes and download the supported versions, see: Corner Bowl Server Manager Downloads