Release Notes are used to communicate changes that will be included in an upcoming Release for the Core Software (including the Document Control QM APP and the Audit QM APP) and the QM APPs.
The table below summarizes the process for publishing Release Notes:
| Communication | Status | When | Where | Comments |
| DRAFT Release Notes (can have multiple iterations) | Approved, Not Effective | When the first version of the Change List is issued and, if required, whenever the Change List is modified | Sent via email to all client Level II Contacts* and published on the Knowledge Base | This is a draft version of what may potentially be included in the Release. It is subject to change. |
| OFFICIAL Release Notes |
Approved & Effective
|
When the Qualification testing is completed | Sent via email to all clients* Level II Contacts** and published on the Knowledge Base and, for the Core Release Notes, the eRoom* | This is considered the final version of the Release Notes and should not change. |
*All clients for the Core Release Notes and impacted clients for the QA APPs Release Notes.
**If you are not a SOLABS Level II Contact and would like to receive the release notes via email, please send an email request to ericka.moore@solabs.com.
The information below provides the detailed process for publishing Release Notes:
The first version of the Release Notes will be issued when our preliminary Core Change List is created. That first version of the Release Notes is issued as a DRAFT document in an Approved, Not Effective Status. It is important to be aware that the changes included in the Release Notes at that moment are not yet ‘Officially’ part of the next Release and that the list CAN change. These Release Notes will be published in the SOLABS’ Knowledge Base. An email will be sent by the Client Success Team to the Level II Contacts that includes a link to the Release Notes.
The Release Notes will include an organized list of the planned fixes to current issues, any new features, and any planned enhancements that are likely to have an impact on clients.
Throughout the development phase for the upcoming Release, the Releases Notes may be updated if a change is added or removed from the Change List. This updated DRAFT version (Approved, Not Effective) will be published in the SOLABS’ Knowledge Base. An email will be sent by the Client Success Team to the Level II Contacts that includes a link to the updated Release Notes.
This process will be followed until the qualification of the new Release is completed. It is possible that during the qualification phase, some changes could be added or removed from the Release. In that case, the DRAFT Release Notes will be updated again.
Once the qualification of the Release is completed, the Official version of the Release Notes will be published in the SOLABS’ Knowledge Base as well as in the Public folder on the eRoom site (for Core Software Release Notes). An email will be sent by the Client Success Team to clients with the link to the final Release Notes.
Comments
0 comments
Please sign in to leave a comment.