Release Cycle

The system receives continuous development, with improvements and fixes deployed regularly.

Update Frequency and Delivery:

• New versions are released frequently as part of a continuous improvement approach, with releases packaged weekly where possible and usually on Thursdays.
• Most updates are delivered without interrupting service or impacting users.

Testing Procedures:

• Each change undergoes rigorous testing, including Integration (White box) testing, QA (Black box) testing, and User Acceptance Testing (UAT) before being released into production.

Deployment Process:

• Updates are deployed during non-working hours.
• They include rollback procedures to allow reversion in the event of unforeseen breakages.

Technology and Security Management:

• The technology stack is continuously updated with the latest stable vendor releases and security patches.
• Patch management is automated where feasible and follows a documented schedule, using official AWS-maintained packages where possible.

Availability and Communication:

• New minor versions are automatically made available to all current users.
• Major platform versions are released gradually through our beta program before being publicly available to switch to.
• Updates are communicated via the Release Notes section of this documentation website.
• New features are comprehensively described as part of our interactive webinar program.

Subscription Benefits:

• These ongoing maintenance, patching, and functional improvements are included as part of the subscription service.