Release Policy

Article author
MCi Notifications
  • Updated

myTrack releases follow a predefined schedule and undergo internal QA testing and signoff prior to deployment in customer environments. The type of release will determine the frequency as well as the communications for that release. All planned releases will occur during the maintenance window which is every Wednesday 8pm - 12am CST and Saturday 8pm - 12am CST*, unless otherwise modified by MCi with prior notification.

 

Release types:

Type Scope Frequency
Critical Urgently address a customer(s) issue that requires immediate attention, and cannot be postponed until a minor release Not planned in advance and should occur infrequently
Minor Address issues that are impacting customers on a planned schedule. These are mostly bug fixes Every 2 weeks
Major New features and functionality that significantly impact business processes

2 - 4 times per year

 

 

Communications per release type:

Type Communications
Critical
  • Release notes will be added to the CSSS at the time of the release or shortly after
  • Customers who submitted tickets will be notified via the ticket that the issue is resolved
Minor
  • Release notes will be added to the CSSS at the time of the release or shortly before
  • Customers who submitted tickets will be notified via the ticket that the issue is resolved
Major
  • Release notes will be added to the CSSS at least 3 weeks in advance of the release
  • Customers will be notified at least 2 weeks before Production release to preview the release in Customer QA

 

*Critical releases may occur outside of the maintenance window due to the impact of the issue it is resolving. If any outage is expected MCi will communicate that outage before it occurs. 

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.