You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The criteria for when changes can be taken into Arcade are as follows. See farther down the document for the bar (criteria) for determining the type of change.
Breaking Changes
Area
When
Notes / Exceptions
Shared Tools
Major version change
Extraordinary business need
Services
Major version change
Extraordinary business need
Backing Resources
Major version change
Extraordinary business need
Guidance
Major version change
Extraordinary business need
Disruptive Changes
Area
When
Notes / Exceptions
Shared Tools
When product is not stabilizing
Should be < 1 a month
Services
When product is not stabilizing
Should be < 1 a month
Backing Resources
When product is not stabilizing
Guidance
Whenever needed
Adoption will take longer
Minimal risk Changes
Area
When
Notes / Exceptions
Shared Tools
Ok in master only
Services
When product is not stabilizing
Backing Resources
When product is not stabilizing
Guidance
Whenever needed
Minor, low risk Changes
Area
When
Notes / Exceptions
Shared Tools
Ok in master only
Services
When product is not stabilizing
Backing Resources
When product is not stabilizing
Guidance
Whenever needed
Bar for determining class of change
Change Type
Criteria
Breaking
Change breaks a scenario, requiring an update by our customer/s
Disruptive
Not necessarily breaking, but there's a high likelihood there will be some unintended fallout OR is a change which adds debt