Overview
This document outlines our current System Development Lifecycle and the Software / QA Validation Process customers can opt to perform for new releases, if you are using a Dedicated Hosting Environment. If you are utilizing our Shared (non-dedicated) Hosting Platform, this validation process likely does not apply.
Step 1 - Testing / Development Environment Release
Testing & Dev
Not publicly accessible to customers
Software Changes, Updates and Bug Fixes developed and tested internally.
After the release is completed and verified internally, a software release is packaged along with Release Notes.
Step 2 - Staging Environment Release
Staging / QA Validation
Access available to Clients with Dedicated Hosting Environments
Once our internal QA team has completed testing, the release will be deployed to the Staging Environment.
Step 3 - Shared Hosting Environment Release (Production)
Shared Hosting Environment
Access available to Shared Hosting clients only.
LabLogs internal QA team will perform one last round of blanket/performance testing in the Staging Environment. If no issues found, we will then promote the release to the Production-level Shared Hosting Environment.
Release notes for the latest Production Shared Hosting Environment release can be found here:
Note: The release notes above ☝️ are published in cadence only with our Shared Hosting (non-dedicated environment ) customers. This means that for Dedicated Environment Platform customers, the most recent release may not be deployed to their dedicated environment yet.
At this stage, our Staging and Production Shared Hosting environments are in sync and the release notes are publically available.
Dedicated Environment admin users will be notified via email that a new release is available. A link to the release notes and QA validation steps for features/enhancements will be provided.
To request an admin user be added to the notification list, submit a ticket through the LabLogs support portal via email or through the ticketing system website.
Support Email:
Subject Line: Dedicated Environment Deployment - Request for Notification [Client Name]
Note: Since new release can often contain important security features, and high-priority bugs, we strongly recommend that Dedicated Environment customers stay up-to-date with the latest release and do not lapse more than one release cycle. In some instances (due to data migrations and other complex deployments) it may be necessary to upgrade a Dedicated Environment in the event that more than one release cycle has lapsed.
Step 4 - Dedicated Environment Release
Dedicated Environment - Client A
Access available to Client A Only
Dedicated Environment - Client B
Access available to Client B Only
Dedicated Environments do not receive the latest Software Release immediately.
The client must submit an official request for Release (details below).
QA/Validation steps will be provided in the release notes linked in the original notification.
As previously mentioned, the client is expected to use the Staging Environment with the Build Release Notes provided with each version and follow the Steps to Validate to internally verify and approve the software release.
Example for Release Notes from Version 1.50
Software Validation Tip:
Testing with the most current Client data is sometimes necessary.
To update the Client data in the Staging Environment, two different options are available to accommodate the software validation process:
1. Data Reset (Most Common)
Upon request, the LabLogs.co support staff can reset the Client data to clear out any outstanding / missed logs that might remain in the system and may have piled up during times of non-use for the Staging Environment. This clears all logs from the system but keeps all Instruments, Sites, Departments and Units. This process is essentially resetting the data to be just like the first-use run of the system.
This is the simplest and most common solution to validate the software release.
2. Data Clone
The LabLogs.co support staff can also clone the client data from the Dedicated Environment(s) to create a more current view of the system. This will pull over a current copy of the data just as it is with recorded logs and all corresponding data.
This can be helpful if many Instruments or Schedule changes have been made since the last validation, but is not typically necessary.
Submitting a Request:
To request a data reset or clone, submit a ticket through the LabLogs support portal via email or through the ticketing system website.
Support Email:
Subject Line: Data Reset [Client Name]
Support Website:
Validation and Approval:
Once the Client has approved the software release build, a formal request must be submitted. This must be done by submitting a ticket through the LabLogs support portal via email or through the ticketing system website.
Support Email:
Subject Line: Software Release [Client Name]
Support Website:
Please reference the Software Release Number and the Client Database.
Requests will only be processed if the ticket is submitted by a verified Administrator User of the Client Site(s).
Turn-around time for a Dedicated Environment Software Releases is 72 hours from time of receipt of Client Request. However, in most cases, this is done much sooner.