Hi,
I'm seeing something in several PRs in flight (and merged) that have
"impact:breaking-change" set, where the purpose of the PR is to fix said
breakage, not introduce API compatibilities.
Am I correct in my understanding that this is not the intended use, and
if so how do we address the misconception?
Can we start by adding a description for the label? It currently has none.
Mu uses "Requires integration attention", which matches my
understanding, but feels a bit abstract. How about
"This change breaks existing APIs"
or
"This change may require corresponding updates to code in other
repositories"?
/
Leif
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#119813): https://edk2.groups.io/g/devel/message/119813
Mute This Topic: https://groups.io/mt/107100295/21656
Group Owner: devel+ow...@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
