- Proposal/Design Review via email to RackHD.CI@emc.etc com
- to ensure no broken impact
- make sure we choosing best & economic solution
- fallback plan is preferred
- Trial Run
- well verify the solution on sandbox jobs or sandbox Jenkins, aim least impact to production business.
- Broadcast
- Notify community via email or slack
- summarize the change & potential impact
- ETA date of the change
- Online & Monitor
- prepare for mitigation, keep old jobs if compatible. and find a easy way as "switch" to switch back to old ways , to ensure smooth business
- production sometimes brings surprise, so putting new feature online to production when early in the morning, so the author can have a whole day to monitor/debug or fallback.
+ Alan Wei + Former user (Deleted)