Releases | Notion

Release Notes:

2.8.0 Release Notes (Latest)

2.6.3 Release Notes

2.2.1 Release Notes

🚀 Intervengine Software Release Process

<aside> ☝

This document outlines the structured process we follow to ensure that every new version of the Intervengine platform is stable, secure, and meets the highest quality standards before being deployed to your production environment.

</aside>

Phase 1: Internal Quality Assurance (QA) & Preparation

Before any new version is considered for release, it must first pass a rigorous internal validation process as a Release Candidate.

This process is designed to catch issues early and ensure the stability and security of the platform. The Release Candidate must successfully pass all of the following checks in our development environment:

Comprehensive Testing: Our internal QA team conducts extensive testing.
Code Linting: Automated checks ensure code is clean, readable, and follows best practices.
Secret Scanning: We scan our codebase to ensure no sensitive credentials or keys have been accidentally included.
Dependency Scanning: We check all third-party libraries for known vulnerabilities.
Security IaC Scanning: Our Infrastructure as Code is scanned for any potential security misconfigurations.
Peer Review: The code is manually reviewed and approved by senior developers.

Only when a Release Candidate has passed every one of these checks is it approved for the next phase.

Phase 2: Staging Deployment

Once a Release Candidate is internally approved, we reserve the right to deploy it immediately to our staging environments.

This allows our team and any clients with staging access, such as yourself, to see the new version in a production-like setting before the official client review period begins.

Phase 3: Client User Acceptance Testing (UAT) & Production Go-Live

This phase is a collaborative effort to ensure you are fully informed, prepared, and satisfied with the upcoming release before it goes live on your production environment.

The UAT Process & Timeline

The entire User Acceptance Testing (UAT) process has a duration of three (3) weeks from the date of notification.

Notification & Documentation (Start of Week 1)
- We will formally notify you that a new production release is planned and publish the official Release Notes.
- You will also be sent two key documents:
  - Testing Spreadsheet: Details the new features and changes for your review.
  - Certificate of Acceptance: The formal sign-off document.
Your Review & Feedback (Weeks 1-2)
- You have a period of two (2) weeks from the notification date to review the upcoming release and return the signed Certificate of Acceptance.
- During this time, you have two options:
  - Option A: Accept Our Testing: You can accept our internal QA testing as sufficient, sign the Certificate of Acceptance, and return it.
  - Option B: Perform Your Own Testing: You can use our Testing Spreadsheet to guide your own internal testing. All feedback and bug reports must be submitted within this two-week window.
Feedback Deadline & Final Release (End of Week 2)
- The deadline for returning the signed Certificate of Acceptance and submitting any feedback or bug reports is the end of the second week.

Scope of Testing & Your Responsibility

Our internal QA process and the provided Testing Spreadsheet cover all generic, platform-wide features.

For any non-generic, client-specific features that have been developed for your organization, it is your responsibility to create and maintain your own testing procedures. Our team does not perform testing on custom features as part of the standard release cycle.

Important: Release Policy

<aside> 🐛

If you report feedback or bugs within the two-week deadline: We will address the issues, which may involve delaying the release to ensure a stable final product.

</aside>

<aside> ⚠️

If the two-week deadline passes without your feedback or a returned certificate: We will proceed with the production release as scheduled at the end of the three-week window. In this event, the liability for any bugs discovered post-release rests with you.

</aside>