Change Process

Owned by Dan Franko (Unlicensed)
Last updated: Aug 11, 2017
1 min read

Ticket

  • Link each items and/or incidents in the release to 
  • List out the update sets in a separate task that need to be applied
  • Attach any data or records that need to be updated to a separate task for each

CAB

Following the typical bi-weekly release scheduled which allows our updates to go in at Thursday night at 8PM is the path of least resistance.  CAB usually just wants a high level explanation of what's being changes and tasks that include testing and communication when necessary.

Release Notes

Keep the release notes KB up to date when releases happen.

Reviewing update sets