Who is this article for?

Client IT/Technical Teams - Those who need to implement technical changes (firewall rules, SSL configurations) 

Client Operations/Management - Decision-makers who need to understand impact and approve changes

No elevated access or permissions are required.

Bulletin Number: TSB-006
Date: May 29th, 2026
Products Affected: Maritime Health (Ideagen Maritime Health), Maritime Health Commercial (Ideagen Maritime Health) & Maritime Safety (Ideagen Maritime Management/Ideagen Maritime Safety)
Version: All versions

Ideagen Maritime Technical Service Bulletin

Purpose

The purpose of this bulletin is to communicate our formalized approach to how defect corrections reported through support will be prioritized, scheduled, and delivered across product versions. As our products continue to mature and our release cadence accelerates, it is essential that both our team and our clients operate under a shared understanding of how and when fixes are delivered. This policy is designed to ensure timely relief for reported issues while allowing our engineering team to remain focused on delivering quality improvements and new capabilities in upcoming releases.

Current Challenges

Ideagen Maritime follows a quarterly major release cycle, with new major versions of our products published approximately every three months. Between major releases, we will issue monthly service releases to deliver defect corrections and targeted optimizations as quickly as possible. This cadence ensures that clients receive frequent, incremental relief for reported issues rather than waiting for the next major release.

Maintaining fixes across multiple older versions introduces significant complexity that directly impacts our ability to deliver stable, high-quality new releases.

Each version we must actively support in parallel divides engineering effort, increases regression risk, and slows delivery of improvements that benefit all clients. For this reason, we are establishing clear guidelines around which versions will receive defect corrections and under what circumstances.

Release Support Policy

Major Releases are published approximately every three months. Each major release includes new features, enhancements, and all previously issued defect corrections.

Service Releases are published monthly for the current major release. These releases are strictly limited to defect corrections and targeted optimizations for issues reported through support. No new features or new functionality will be introduced in a service release. This ensures that service releases remain low risk and focused solely on improving the stability and reliability of your current environment. Monthly service releases will continue until the next major release is published, at which point service releases will shift to the new major version.

Defect Corrections for issues reported through support will be prioritized and delivered in the next service release associated with the current major release. If a defect is reported against an older major release that has already been superseded, the fix will only be included in the current service release or the upcoming major release, not retroactively applied to the older version.

Critical Security Vulnerabilities and P1 Support Incidents are the sole exceptions to this policy. A P1 support incident is defined as a complete loss of mission-critical functionality with no viable workaround, a defect that introduces a regulatory or compliance exposure, or an issue that directly impacts financial or billing operations within the application. If a critical security flaw is identified, or a defect meets the P1 criteria as agreed upon by both Ideagen Maritime and the client, Ideagen Maritime will issue targeted hotfixes or service releases for the previous two major releases. These exceptions exist to protect client environments that may not yet have completed their upgrade process and to ensure continuity of essential operations. If a client believes a defect should be prioritized outside of the standard policy, they may submit a request through their Customer Success Manager with clear justification and documented evidence of the impact to their operations. Ideagen Maritime will evaluate these requests on a case-by-case basis.

All Other Defects, including UI, UX and general functionality issues, will be addressed in the current major version's next scheduled service release or in the upcoming major release. Fixes will not be backported beyond one prior version. The critical security and P1 exceptions described above are the only circumstances under which older versions will receive targeted fixes.

Why Upgrading Matters

We strongly encourage all clients to upgrade to the latest major release as soon as it becomes available. Even if your organization does not plan to adopt new features immediately, upgrading ensures that you benefit from all accumulated defect corrections, performance improvements, and security patches delivered through service releases.

Clients should not fall more than two major releases behind the current release. With major releases published approximately every three months, this means clients have roughly six months from the publication of a new major release to complete their upgrade before their current version falls outside the active support window. Our ability to investigate, reproduce, and resolve defects reported against older versions is limited when those versions are no longer actively developed. If your environment is more than two versions behind and you report an issue, the correction will be delivered in the current or upcoming release, not backported to your version. In these cases, upgrading will be the recommended path to resolution.

Staying current gives your organization the highest quality experience, the fastest path to resolution when issues arise, and ensures our engineering team can focus efforts on delivering improvements that benefit all clients.

Summary

Example: Where Will My Fix Be Delivered?

The following table illustrates how defect corrections are distributed across versions based on severity. In this example, the current environment is as follows:

• Current major release: v3.0.0
• Previous major release: v2.24.0
• Next major release in development: v3.1.0

Monthly service releases (v3.0.1, v3.0.2, v3.0.3, etc.) will be published for the current major release until the next major release (v3.1.0) is published.

Release Notes & Notifications

Every release will be accompanied by release notes detailing all defect corrections included in that release. Release notes will be published on the day of the release on the Ideagen Luminate portal and can also be accessed through the Self-Release Admin within your application.

We strongly encourage clients to subscribe to release notifications so that your team is alerted as soon as a new version is available for download. These email notifications include direct links to the corresponding release notes. To enable this notification, log into your Operations environment for your respective product and navigate to Admin > Notifications. Search for "New Software Update Available" and subscribe to begin receiving alerts.

Next Steps

We understand that upgrade planning requires coordination, and our team is here to support you through that process. If you have questions about this policy, need assistance planning an upgrade, or wish to discuss your current version status, please open a support ticket or reach out to your Customer Success Manager.

Disclaimer

This bulletin is intended for informational purposes and reflects Ideagen Maritime's current release support policy as of the date of publication. Ideagen Maritime reserves the right to modify this policy as needed to ensure the security and quality of our products. Clients are encouraged to open a support ticket or contact their Customer Success Manager with any questions or concerns.