From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: Michael Kubacki <mikuback@linux.microsoft.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"gaoliming@byosoft.com.cn" <gaoliming@byosoft.com.cn>,
"rfc@edk2.groups.io" <rfc@edk2.groups.io>
Cc: 'Andrew Fish' <afish@apple.com>,
'Leif Lindholm' <quic_llindhol@quicinc.com>,
'Sean Brogan' <sean.brogan@microsoft.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: 回复: [edk2-devel] [RFC] Transitioning from Bugzilla to GitHub Issues
Date: Fri, 16 Aug 2024 21:32:14 +0000 [thread overview]
Message-ID: <CO1PR11MB4929A2FB70465B64C8035031D2812@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <83e432d5-08f0-4746-956e-5967d7b2b23d@linux.microsoft.com>
Another option to consider for all Code First tasks is to
use PRs against the edk2 repo. PRs can be synced periodically
and can be in open state until the spec updates are public and
then merged into edk2.
Mike
> -----Original Message-----
> From: Michael Kubacki <mikuback@linux.microsoft.com>
> Sent: Friday, August 16, 2024 12:54 PM
> To: devel@edk2.groups.io; Kinney, Michael D <michael.d.kinney@intel.com>;
> gaoliming@byosoft.com.cn; rfc@edk2.groups.io
> Cc: 'Andrew Fish' <afish@apple.com>; 'Leif Lindholm'
> <quic_llindhol@quicinc.com>; 'Sean Brogan' <sean.brogan@microsoft.com>
> Subject: Re: 回复: [edk2-devel] [RFC] Transitioning from Bugzilla to GitHub
> Issues
>
> On 8/14/2024 11:49 PM, Michael D Kinney wrote:
> >
> >> -----Original Message-----
> >> From: Michael Kubacki <mikuback@linux.microsoft.com>
> >> Sent: Wednesday, August 14, 2024 7:30 PM
> >> To: devel@edk2.groups.io; gaoliming@byosoft.com.cn; Kinney, Michael D
> >> <michael.d.kinney@intel.com>; rfc@edk2.groups.io
> >> Cc: 'Andrew Fish' <afish@apple.com>; 'Leif Lindholm'
> >> <quic_llindhol@quicinc.com>; 'Sean Brogan' <sean.brogan@microsoft.com>
> >> Subject: Re: 回复: [edk2-devel] [RFC] Transitioning from Bugzilla to
> GitHub
> >> Issues
> >> On 8/6/2024 1:34 AM, gaoliming via groups.io wrote:
> >>> Michael:
> >>> Thanks for your great effort. This is a good direction to
> consolidate
> >> code and issue together. My feedbacks are below:
> >>>
> >>> 1. BugZilla supports code first process. What proposal will handle this
> >> process in Github issue flow?
> >>
> >> For the Tianocore specifications, the proposal is that each respective
> >> repository in the tianocore-docs organization
> >> (https://github.com/tianocore-docs) maintain their issues.
> >>
> >> I'm open to suggestions for the UEFI Specification issues.
> >
> > Code first has 2 categories. One is for spec changes and the other
> > is for the code changes associated with the spec changes.
> >
> > Code first uses branches in the edk2-staging repo, so perhaps all
> > code first related bugs should migrate to the edk2-staging repo.
> >
> > We do want to make these very visible and have ways to integrate/test
> > code first changes with latest edk2 repo content. SO perhaps we can
> > have a wiki page or discussion with active code first branches.
>
> I updated the RFC to mention the edk2-staging repo approach and the need
> to migrate to the appropriate repository.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120362): https://edk2.groups.io/g/devel/message/120362
Mute This Topic: https://groups.io/mt/107746608/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2024-08-16 21:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 21:20 [edk2-devel] [RFC] Transitioning from Bugzilla to GitHub Issues Michael Kubacki
2024-07-29 23:28 ` Michael D Kinney
2024-07-31 14:41 ` Michael Kubacki
2024-07-31 17:56 ` Michael D Kinney
2024-07-31 19:36 ` Michael Kubacki
2024-08-06 5:34 ` 回复: " gaoliming via groups.io
2024-08-15 2:29 ` Michael Kubacki
2024-08-15 3:49 ` Michael D Kinney
2024-08-16 19:53 ` Michael Kubacki
2024-08-16 21:32 ` Michael D Kinney [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=CO1PR11MB4929A2FB70465B64C8035031D2812@CO1PR11MB4929.namprd11.prod.outlook.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