Deployment Process v6.9.5 and v7

This provides an overview of the steps for deploying code (packages) for v6.9.5 and v7.

1. Person deploying code to production is responsible for:

   1. Reviewing changes committed between version of package in production and version being deployed to production in advance of scheduled deployment time.  This applies to all packages being deployed.
   2. Understanding impact of each change
   3. Creating checklist for changes requiring manual updates and ensuring either they or another member of the team are able to make the changes immediately after deployment (encourage dev team to use deploy notes to assist with this). Using the Change Request document can help with this.

   4. Being able to effectively troubleshoot a post deployment issue including having ability to quickly rollback changes.

2. If an emergency fix is needed, developer should:

   1. Create JIRA ticket for the fix
   2. Create a Ticket-based branch off the changeset corresponding to current production release version. 
   3. Build new release version against this branch
   4. Deploy to dev
   5. Verify
   6. Deploy to production
   7. Merge into main branch.
      NOTE:  If the emergency fix is a non-compiled change that can be safely made in production to address the immediate issue, it can be.  However, the above steps must still be completed sans redeploying to production.
3. Creating Ticket-based branches during standard dev cycle is at the discretion of the tech lead/project team.
4. If we do branch, we should use ticket-based branching to tie the branch to a specific work item.