Discussion on tracking / preserving user interfaces and their contracts with minimal breaking changes.
RackHD CC slack channel discussion on impactful changes. Symphony escalation this week that found a service naming change. We should define what breaking changes are (service, task, workflow naming for example), how best they can be preserved (automatic checks?), and ways to communicate changes (programmatically, broadcast on the slack channel, etc....)
Team agreed to improve github messages to highlight the changes.
These are the names we want to highlight / escalate changes:
workflow names, service names, configuration changes, task names
if changing the purpose of any of the above, better to create a new one. Need to preserve backwards compatibility
As part of Sprint Release migration to the Regression-Baremetal job, Look to generate release notes from github messages + template instead of Jira stories (AI: James Turnquist).
On-web-ui long term plan update
AI from last week: Former user (Deleted)to review list below to see if there are any centurylink issues that are already in the list. Plan to create PRs for the known issues worked on with Centurylink.
Completed, we have issues covering all the escalated centurylink issues.
Should Force merge to master be allowed in the new CD model?
Geoffrey Reid to check to see if this can be disabled
Force pushes are re-writing history on master, should use a revert that won'd delete the commit history. Builds without source can exist.
AI: Amy to send out poll to CC team to move meeting to a different day as it conflicts with the Arch meeting. Also, need to account for daylight savings time occurring on 11/5.