Is there a documented change and release management process? How are updates managed?

Yes, there is a documented change and release management process for the myosh system. The system undergoes continuous development, with improvements and fixes deployed regularly.

Update Frequency and Delivery

New versions are released frequently as part of a continuous improvement approach. Releases are packaged weekly where possible, typically on Thursdays. Most updates are delivered without interrupting service or impacting users. These ongoing maintenance, patching, and functional improvements are included as part of the subscription service. 1

Testing Procedures

Each change undergoes rigorous testing before being released into production. The testing process includes:

• Integration (White box) testing
• QA (Black box) testing
• User Acceptance Testing (UAT)

1

Deployment Process

Updates are deployed during non-working hours and include rollback procedures to allow for reversion in the event of unforeseen issues. 1

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 when possible. 1

Availability and Communication

New minor versions are automatically made available to all current users. Major platform versions, like Viking 2.0, are released gradually through a beta program before being made publicly available. 1

Updates are communicated via the Release Notes section of the documentation website. New features are also described as part of an interactive webinar program. 1