public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Jin, Eric" <eric.jin@intel.com>
To: Supreeth Venkatesh <Supreeth.Venkatesh@arm.com>,
	Leif Lindholm <leif.lindholm@linaro.org>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	Dong Wei <Dong.Wei@arm.com>, "Jin, Eric" <eric.jin@intel.com>
Subject: Re: SCT bugzilla topic?
Date: Mon, 10 Dec 2018 02:18:55 +0000	[thread overview]
Message-ID: <DA72DC7456565B47808A57108259571F63721913@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <AM4PR08MB2788D19C9CB3E5787300986E80AE0@AM4PR08MB2788.eurprd08.prod.outlook.com>

Supreeth and Leif,

UEFI-SCT is open source project now, the mantis is not proper option. We had better use the Bugzilla as edk2.
Could the stewards help to create the Edk2 Test Product and SCT component if most members want to split test with edk2?

Best Regards
Eric

-----Original Message-----
From: Supreeth Venkatesh <Supreeth.Venkatesh@arm.com> 
Sent: Tuesday, December 4, 2018 3:37 AM
To: Leif Lindholm <leif.lindholm@linaro.org>; edk2-devel@lists.01.org
Cc: Jin, Eric <eric.jin@intel.com>; Kinney, Michael D <michael.d.kinney@intel.com>; Dong Wei <Dong.Wei@arm.com>
Subject: RE: SCT bugzilla topic?

Leif,

Earlier, we used to use UTWG Mantis (for feature requests - https://mantis.uefi.org/mantis/view.php).
After, UEFI-SCT became Open source, we did discuss to have the same infrastructure setup as edk2, which means using Bugzilla.
However, I don't think we have created a SCT component or Edk2 Test Product yet.

Your email reminds me one more task after the SCT component / Edk2 Test product is created i.e., to migrate over remaining UTWG issues to Bugzilla.

Once Eric chimes in/agrees, we will request Mike to create Edk2 Test Product within Bugzilla.

Thanks,
Supreeth

-----Original Message-----
From: Leif Lindholm <leif.lindholm@linaro.org>
Sent: Monday, December 3, 2018 8:47 AM
To: edk2-devel@lists.01.org
Cc: Eric Jin <eric.jin@intel.com>; Supreeth Venkatesh <Supreeth.Venkatesh@arm.com>; Michael D Kinney <michael.d.kinney@intel.com>
Subject: SCT bugzilla topic?

Hi Eric, Supreeth, Mike,

I was looking to raise a feature request on UEFI SCT and didn't spot such a product. Should we create one?

Or perhaps we should have an EDK2 Test product with an SCT component?

Regards,

Leif
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.


  reply	other threads:[~2018-12-10  2:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03 14:46 SCT bugzilla topic? Leif Lindholm
2018-12-03 18:30 ` Richardson, Brian
2018-12-03 19:36 ` Supreeth Venkatesh
2018-12-10  2:18   ` Jin, Eric [this message]
2018-12-10  3:02     ` Kinney, Michael D
2018-12-10  8:13       ` Leif Lindholm
2018-12-10  8:43         ` Jin, Eric
2018-12-10 16:40           ` Supreeth Venkatesh
2018-12-10 17:37             ` Kinney, Michael D
2018-12-10 17:51               ` Supreeth Venkatesh

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=DA72DC7456565B47808A57108259571F63721913@SHSMSX103.ccr.corp.intel.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