Marking large design changes as major #4881
gfellerph
announced in
Architecture Decisions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Context
We received a lot of feedback from Design Changes that were released under patch or minor versions but changed the appearance of components in a major way (#3490).
Decision
We are marking major Design Changes as major change with changesets.
Consequences
Major Design Changes that would not break the technical implementation will have to be buffered together with other, technically breaking changes, potentially delaying their release.
Example (optional)
New disabled styles with dotted border and stroke. That change sparked a lot of controversy.
Beta Was this translation helpful? Give feedback.
All reactions