Product Release Cycle Overview

Purpose Statement

This article outlines the release cycle for new features and updates within the platform
It explains how users can preview upcoming changes in a test environment before they are deployed to production
The goal is to provide transparency, reduce disruption, and allow agencies to prepare for changes in advance

To improve stability and user readiness, releases are now deployed in two phases:
- Test Environment Release: 1st of each month (or next business day)
- Production Release: 15th of each month (or next business day)
This staggered approach gives users approximately two weeks to:
- Explore new features
- Validate workflows
- Train personnel
Agencies are encouraged to actively use test environments as part of their standard workflow for change management and training

Start of Month
- New features and updates are deployed to test environments only
- Review the Release Notes section of the Knowledge Base for details on new features, enhancements, and changes
Testing Period (~2 Weeks)
- Users can:
  - Log into the test environment
  - Evaluate new functionality
  - Add test personnel
  - Run simulated workflows
- If assistance is needed:
  - Submit a support ticket if you have any issues accessing your test environment or new features
  - Contact your Client Success Manager for guidance
Mid-Month Release
- Updates are promoted to the production (live) environment
- Changes become live for all users

NOTE: Bug fixes, critical updates, and regular maintenance will still be deployed on a rolling basis.

To fully utilize the release cycle, review the following articles:

Test Environments Overview:
Learn how to access and use your department’s test environment
USA Test Daily:   https://testdaily.firstdue.com/
USA Test: https://test.firstdue.com/
Canada Test Daily:   https://testdaily-canada.firstdue.com/
Canada Test:   https://test30-canada.firstdue.com/
For more information on Test Environments check here.
Adding Personnel to the System:
Add users to the test environment to safely evaluate new features (if they are not in your live environment)
- Personnel Record: Creating a New Record
Submit a Support Ticket
- If you have any issues accessing your test environment or new features

Regularly review the Release Notes at the beginning of each month
Log into the test environment early to explore updates
Assign a small group (e.g., training officers or supervisors) to review updates first
Add test personnel accounts to simulate real-world usage
Communicate upcoming changes internally to prepare field users

Q: Do changes made in the test environment affect production?

Q: Who should be using the test environment?

Training officers, administrators, and supervisors are ideal users for early evaluation

Q: What should we do if we find a bug?

Submit a support ticket with as much detail as possible, including steps to reproduce the issue

Q: Where can we see what’s included in each release?

Review the Release Notes section of the Knowledge Base for a full breakdown of features and updates

Q: Who do we contact if we need help understanding a feature?