public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael Kubacki" <mikuback@linux.microsoft.com>
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
Date: Wed, 14 Aug 2024 22:29:48 -0400	[thread overview]
Message-ID: <c9d0f661-9fac-4576-b96a-a11d29630a1f@linux.microsoft.com> (raw)
In-Reply-To: <01f901dae7c2$483622b0$d8a26810$@byosoft.com.cn>

Hi Liming,

I apologize for the delayed response.

Thanks,
Michael

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.

> 2. BugZilla supports Edk2-Platform and Edk2-Test repo. After their issues are migrated to Github, their code process will be migrated to Github pull request. Right?

Yes. The RFC focuses on edk2 right now, but that would be the plan as 
we're trying to consolidate process across the repos. For clarity, I 
will add that as a section in the RFC.

> 3. Edk2 Stable Tag Release Note will list the resolved issue and feature. I think they can be found in GitHub issue. I will learn the way how to find them.

We'll have many options to streamline this process. We can create a 
single dashboard that can show issues from all the repos if that helps 
and I think we'll be able to better track issues to features and code 
changes for the reasons mention in the RFC.


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120342): https://edk2.groups.io/g/devel/message/120342
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]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2024-08-15  2:29 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 [this message]
2024-08-15  3:49             ` Michael D Kinney
2024-08-16 19:53               ` Michael Kubacki
2024-08-16 21:32                 ` Michael D Kinney

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=c9d0f661-9fac-4576-b96a-a11d29630a1f@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