Introduce suspension of changes and releases during important events
During the livestream on 2018-09-20 we decided to suspend a network configuration change and I think it might be worth discussing a way to formalize this process.
What we need:
- something to call it
- something that is accessible for the team and company to view
- something we can query from CICD to stop our automated changes from rolling out
For (1) we could call it Production SOC (suspension of changes) though it is not a standard term. We should avoid other popular terms like "blackout windows" or "blackdays". I did some googling around and couldn't find anything that is standard and would love to hear suggestions.
For (2) I would like to signal boost this but putting it on the shared meeting calendar, if that is a bit too much we could create a new calendar for it.
For (3) would a google calendar work or should we consider other options? the last internal company pipeline tool I used had a feature where you could force pipelines to pause during the certain time intervals, @ayufan is there anything like this on the roadmap for cicd?
Name suggestions (feel free to vote or add more if you have them)
- SOC (suspension of changes)
👻 - Change suspension
🌴 - office hours
🎢 - ICL (Infrastructure Change Lock)
🎱 - Change freeze
⛄