From: "Michael D Kinney via groups.io" <michael.d.kinney=intel.com@groups.io>
To: gaoliming <gaoliming@byosoft.com.cn>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] TianoCore Bugzilla to Github Issues Migration is complete
Date: Sat, 21 Dec 2024 03:09:43 +0000 [thread overview]
Message-ID: <CO1PR11MB4929C81B62683D8DEFB0B0BCD2002@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <000201db534f$f2ee0ad0$d8ca2070$@byosoft.com.cn>
Hi Liming,
Good questions. Responses below.
Mike
> -----Original Message-----
> From: gaoliming <gaoliming@byosoft.com.cn>
> Sent: Friday, December 20, 2024 6:28 PM
> To: devel@edk2.groups.io; Kinney, Michael D <michael.d.kinney@intel.com>
> Subject: 回复: [edk2-devel] TianoCore Bugzilla to Github Issues
> Migration is complete
>
> Mike:
> I do the quick check. There is no missing items. Now, I have two
> questions
> here.
>
> 1. If the issue has been assigned to the person, I can find the person
> name
> in the issue, but the person name is not in issue assignee field.
> Seemly, we
> still need to manually assign them.
Correct. The migration tool attempted to cross reference to active
community members with known GitHub IDs. If that mapping was not available
then it is left unassigned and will need to be assigned to an active
community member.
>
> 2. If the issue has pull request, its PR has not related to this issue.
> For
> example, Bugzilla 4949 is migrated to
> https://github.com/tianocore/edk2/issues/10539, its PR
> https://github.com/tianocore/edk2/pull/6545. How group them together?
The PR can reference the GitHub issue with #<Issue ID>
The Bugzilla ID number is part of the GitHub Issue Title, so if
Anyone needs to search for an issue by Bugzilla ID, they can use
the GitHub issue search and search for "Bugzilla Bug <BZ ID>"
>
> Thanks
> Liming
> > -----邮件原件-----
> > 发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Michael D
> > Kinney via groups.io
> > 发送时间: 2024年12月21日 8:01
> > 收件人: devel@edk2.groups.io
> > 抄送: Kinney, Michael D <michael.d.kinney@intel.com>
> > 主题: [edk2-devel] TianoCore Bugzilla to Github Issues Migration is
> complete
> >
> > Hello,
> >
> > The migration of all issues from TianoCore Bugzilla to GitHub Issues
> > is complete. All the open and closed issues have been migrated to the
> > appropriate repository in GitHub.
> >
> > GitHub issue templates are now active.
> >
> > Please let us know if there is any information missing or there are
> > any problems using GitHub issues for all bug reports and feature
> > requests.
> >
> > The TianoCore Bugzilla server can no longer be accessed.
> >
> > Thanks,
> >
> > Mike
> >
> >
> >
> >
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120930): https://edk2.groups.io/g/devel/message/120930
Mute This Topic: https://groups.io/mt/110225390/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-12-21 3:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 0:00 [edk2-devel] TianoCore Bugzilla to Github Issues Migration is complete Michael D Kinney via groups.io
2024-12-21 2:27 ` 回复: " gaoliming via groups.io
2024-12-21 3:09 ` Michael D Kinney via groups.io [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=CO1PR11MB4929C81B62683D8DEFB0B0BCD2002@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