Release process for Limio Commerce

The changes we've to our release process enhance efficiency and stability. Here's a quick guide to our new approach:

Limio Process

Development Duration:

Each release now undergoes a 4-week development phase, providing more time for improvements compared to the previous 2-week cycle.

Seamless Transitions:

To ensure a smooth transition, we create a new release environment before the current release is complete. This allows for a seamless handover and minimal disruptions.

Testing Phases:

1. Limio Release Environments: Development and unit testing take place in the release environments. Once a ticket is complete it's promoted to our sandbox
   
   
2. Limio Sandbox: Regression testing happens here, ensuring a robust release
   
   
3. Customer Non-Production: User Acceptance Testing (UAT) occurs in this environment to simulate real-world scenarios
   
   
4. Customer Production: The final release is deployed to the customer's production environment

Stages in a Release:

1. Week 1-3: Development in the release environment
2. Week 4: Closing tickets in the current release environment. No new tickets to that environment
3. Week 5-6: Regression testing in Sandbox
4. Week 7: Release is available to customers for UAT and production adoption

To enlarge image: right click > open image in new tab

Customer Process

1. Customer requests via Limio support for QA/Dev to be updated to the new release
2. Customer tests in QA/Dev, paying special attention to Custom Components and flows
3. If regression bugs are found, the customer raises a support ticket
4. Limio investigates and works on a fix for the regression issue
5. Customer tests regression fix in QA/Dev
6. Customer requests via Limio support for Prod to be updated to the new release

To enlarge image: right click > open image in new tab

To receive notifications when we publish release notes, Follow our Release Notes page.

See our estimated release dates here: 

• 2023 Release Schedule
• 2024 Release Schedule