Activator 3 Releases

Activator v3 marks a significant transition from a single-tenant PaaS model to a multi-tenant SaaS platform, streamlining the infrastructure while maintaining robust content repository integration for our Life Science clients. This evolution necessitates a new release management strategy, reflecting the shift from individualized client releases to a unified approach.

Activator v3 is a multi-tenant SaaS platform where all clients operate on the same shared frontend and infrastructure. This architecture enables streamlined updates and consistent delivery of features and fixes across all users.

Our release process balances regular updates with a commitment to ensuring stability and reliability.

Release Frequency

Before the Activator 3.0.0 Release

During the development phase leading up to the major release 3.0.0, updates are aligned with our sprint cycles:

• Sprint-Based Releases: Updates are released every 14 days, following the completion of each sprint.

• Incremental Versions: Release notes are published at the end of each sprint, providing details on what was included in the current release. While updates are based on a roadmap, specific features are not guaranteed.

• These releases may include:

  • Feature Enhancements: New capabilities or improvements to existing features.

  • Bug Fixes: Resolutions for known issues.

  • Infrastructure Updates: Performance optimizations and backend improvements.

If a release fails validation, it will be skipped. The next scheduled release will occur at the end of the following sprint (14 days later).

After the Activator 3.0.0 Release

Once Activator 3.0.0 has been solidified and released, we will transition to a traditional major, minor, and patch release cycle. The exact frequency of these releases will be determined closer to the launch date.

Release Lifecycle

Development and Validation

• Updates are thoroughly tested during development and staging to ensure stability and compatibility with all clients’ use cases.

• Validation focuses on ensuring all tenants function seamlessly before deployment.

Environment Rollouts

1. STG (Staging Environment): Releases are first deployed here for internal testing and review. Deployment to STG is based on readiness and may not follow a strict schedule.

2. PROD (Production Environment): Updates are deployed live only after passing all validation checks on STG.

Deployment Principles

With Activator v3’s multi-tenant structure:

• Shared Updates: All clients receive updates simultaneously, ensuring consistency across the platform.

• Stability Focus: Only thoroughly validated releases are deployed to production to minimize disruptions.

• Non-Experimental Features: All features included in releases are stable and intended for immediate client use.

Release Notes

Release notes are made available at the conclusion of each sprint. They summarize:

• Features added or enhanced.

• Issues resolved.

• Any notable backend or infrastructure improvements.

Release notes are the definitive source for understanding what has been included in each update.

All release notes can be found here: Activator 3 Release Notes.

Release Schedule