public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael Kubacki" <mikuback@linux.microsoft.com>
To: Leif Lindholm <quic_llindhol@quicinc.com>, devel@edk2.groups.io
Cc: "discuss@edk2.groups.io" <discuss@edk2.groups.io>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] github impact:breaking-change
Date: Tue, 9 Jul 2024 11:12:41 -0400	[thread overview]
Message-ID: <8ccef149-fbde-46c6-9fd9-57fc39e99b04@linux.microsoft.com> (raw)
In-Reply-To: <Zo1RQi3jz394SefJ@qc-i7.hemma.eciton.net>

The tweaks look good to me.

Thanks,
Michael

On 7/9/2024 11:03 AM, Leif Lindholm wrote:
> Hi Michael,
> 
> On Tue, Jul 09, 2024 at 10:44:46 -0400, Michael Kubacki wrote:
>> Hi Leif,
>>
>> Thanks for raising this. The label was intended to be set from the PR
>> template which has an explanation:
>>
>> https://github.com/tianocore/edk2/blob/master/.github/pull_request_template.md
>>
>> If the breaking change box is checked, it will be added automatically.
> 
> Right, so it seems some people have misunderstood the description in
> the template.
> 
> The current text is
> "Breaking change - Will this cause a break in build or boot behavior?"
> 
> I raised https://github.com/tianocore/edk2/pull/5895 for some minor
> language tweaks that hopefully reduce the risk of misinterpretation.
> 
>> I added a description in GitHub for the label as well:
>>
>> https://github.com/tianocore/edk2/labels
> 
> Thanks!
> 
> Regards,
> 
> Leif
> 
>>
>> Thanks,
>> Michael
>>
>> On 7/8/2024 7:00 AM, Leif Lindholm wrote:
>>> 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 (#119852): https://edk2.groups.io/g/devel/message/119852
Mute This Topic: https://groups.io/mt/107100295/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



      reply	other threads:[~2024-07-09 15:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-08 11:00 [edk2-devel] github impact:breaking-change Leif Lindholm
2024-07-09 14:44 ` Michael Kubacki
2024-07-09 15:03   ` Leif Lindholm
2024-07-09 15:12     ` Michael Kubacki [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8ccef149-fbde-46c6-9fd9-57fc39e99b04@linux.microsoft.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox