Home Useful Articles
My Group: This user has no roles.
My Distribution ID: Please log in to see your distribution ID.
Open TOC

Page Contents

 

Understanding NIVOMAX Software Versioning and Release Strategy

Disclaimer

SYNAXIOM does not distribute NIVOMAX Viewer setup files directly to end users. To obtain the necessary setup files, users must download a copy directly from the Technical Publications Supplier's NIVOMAX Self Serve portal, subsequent to agreeing to the terms and conditions stipulated therein. The Technical Publication Supplier, possessing a valid Distribution ID for their copy of the NIVOMAX Applications, is the sole distributor. Access to and use of the NIVOMAX Viewer is contingent upon the purchase of a Data License for a digital product from the Technical Publications Supplier. The digital product downloaded will function exclusively with the viewer provided by the respective Supplier. Users are advised that the distribution of NIVOMAX Viewer setup files may be governed by applicable export control regulations depending on their region.

Licensing

It is not necessary for end-users to purchase a separate NIVOMAX license. The Technical Publications Supplier from whom you have acquired your Data License has already procured the requisite licenses from SYNAXIOM. By extending an invitation, they include you within their authorized user pool, as permitted under their NIVOMAX license agreement. You are authorized to use the NIVOMAX software provided the Technical Publications Supplier maintains a valid NIVOMAX software license.

Confidentiality

This document (“Document”) contains confidential and proprietary information owned by SYNAXIOM Inc. (“SYNAXIOM”). No part of this Document may be reproduced, copied, or distributed in any form or by any means without the prior written permission of SYNAXIOM Inc. Unauthorized use, disclosure, or reproduction of this Document is strictly prohibited. Any third-party intellectual property mentioned herein is the property of their respective owners, and such mention is for informational purposes only and does not imply any association with or endorsement by the owners.

This page must not be removed before distributing the document. It must remain present in all shared copies to ensure proper communication and compliance.

Understanding NIVOMAX Software Versioning and Release Strategy

Last Updated on March 11, 2025 | 4 min read

In this article, we will clarify how NIVOMAX Software platform’s versions and patches are structured. You’ll learn about our main (upgrade) releases, the quarterly patch cycles, and how we label each one for maximum clarity. By the end, you’ll understand how we ensure stability, security, and rapid iteration across our entire platform.

1. Upgrade Releases

1.1 What Are Upgrade Releases?

Upgrade Releases are the primary upgrade versions of our platform, scheduled periodically throughout the year. Upcoming release dates are published on the NIVOMAX Help Center for transparency and planning. Each major release may introduce:

  • New Features that enhance functionality and user experience
  • Architectural Improvements for better performance, scalability, and security
  • Significant Updates addressing system-wide enhancements or integrations

These releases set the foundation for ongoing improvements, with maintenance and patch updates ensuring stability between major upgrades.

1.2 Naming Convention

We denote major releases by Year-SequenceNumber. Examples include:

  • 2024-1
  • 2024-2
  • 2025-1

2. Quarterly Maintenance Releases (QMR)

Quarterly Maintenance Releases are also known as Patch Releases.

2.1 Purpose of Quarterly Patches

Our platform follows a scheduled quarterly maintenance cadence. These Quarterly Maintenance Releases (QMR) focus on:

  • Bug Fixes
  • Security Updates

2.2 Naming Convention

To avoid confusion, the naming of a QMR ties directly to the major release it patches. We use the format:

<Major Release> QMR<sequenceNumber>

For example:

  • 2024-2 QMR1 – The first quarterly maintenance release for the 2024-2 platform version.
  • 2024-2 QMR2 – The second quarterly maintenance release for the 2024-2 platform version.

QMR versions are released until the next Upgrade Release is issued.

3. Handling Critical Individual App Patches

3.1 Why We Have Individual App Patches

Within our platform, we have multiple modular applications (e.g., a Builder app, a Viewer app). In rare cases, a critical bug or security vulnerability might require an urgent patch for just one app, rather than for the entire platform.

3.2 When These Are Released

  • Outside of Quarterly Maintenance – When time-sensitive, a standalone patch is released immediately rather than waiting for the next scheduled QMR.
  • Within the Quarterly Cycle – If the issue can safely wait until the next QMR, the fix will be bundled with the usual quarterly maintenance updates.

3.3 Naming Convention

Individual app patches often include the major release they are built on plus an additional increment or descriptor—for example:

  • NIVOMAX Viewer 2024-2-QMR1  v.1.5.13

4. Avoiding Confusion Between Years and Releases

4.1 Year-Based Naming vs. Actual Target

A common source of confusion is when a patch for a specific major release in one year spills over into the next calendar year. Our naming convention solves this by always referencing the original major release.

4.2 Example Scenario

December 2024: We release 2024-2.
February 2025: We push a patch named 2024-2 QMR1.

5. Summary of Benefits

  • Clarity of Versions: By always referencing the underlying major release (e.g., “2024-2 QMR1”), there’s never ambiguity about which platform version the patch updates.
  • Predictable Schedules: Quarterly maintenance releases (QMRs) provide a known roadmap for security fixes and minor enhancements.
  • Rapid Response to Critical Issues: Individual apps can be patched separately, preventing major disruptions while swiftly addressing critical bugs.
  • Year-Based Major Versions: The year in the name helps plan migrations and aligns stakeholders on when major updates will occur.

6. Frequently Asked Questions

Q: What if there’s a critical fix needed during a Quarter?
A: We release an immediate patch specifically for the impacted app. If a platform-wide issue arises, we issue an unscheduled QMR if it’s urgent enough, or we include it in the next QMR if it can wait.

Q: Can I skip a QMR and go straight to the next major release?
A: Yes but we strongly recommend applying each QMR to maintain security and stability. Patches often address vulnerabilities that could impact your system.

Q: How do I know which QMR applies to my current platform version?
A: Each QMR name references the major release (e.g., “2024-2 QMR1,” “2024-2 QMR2”). Match the major release number in your environment to the QMR you need.

Conclusion

Our versioning system uses year-based major releases and explicitly labeled quarterly maintenance releases (QMRs) to keep software updates straightforward, predictable, and secure. By linking patches directly to their major release, we remove confusion over which version is maintained, even if release timelines cross into new calendar years.

For the latest documentation on this and other important topics, please refer to the NIVOMAX Help Center. The NIVOMAX Help Center is your primary resource for up-to-date information, guidelines, and self-serve support for NIVOMAX.

This document also has an online version which may be more up-to-date.
 

Guides

NIVOMAX © 2017-2025 All rights reserved SYNAXIOM INC.
© 2005 – 2025 SYNAXIOM Inc.
Usage of this site constitutes acceptance of our Intellectual Property Policy; please ensure you have read it thoroughly.

CONFIDENTIAL

This document is the property of SYNAXIOM Inc.

NIVOMAX © 2017-2025 All rights reserved SYNAXIOM INC. © 2005 – 2025 SYNAXIOM Inc.
Usage of this document constitutes acceptance of our Intellectual Property Policy; please ensure you have read it thoroughly.

Uncontrolled copy generated on: 2025-03-14 09:02:23