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

Thanks Mike.
Looks good to me. I guess we can populate version field later to v2.7.0 (or something other than "UNSPECIFIED" later) .

Leif,

Please go ahead and raise a feature request and let us know.

Supreeth

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

Supreeth,

I have created the "EDK2 Test" product with the "UEFI-SCT" component.

Please review and let me know if there are any additional changes required.

Best regards,

Mike

> -----Original Message-----
> From: Supreeth Venkatesh
> [mailto:Supreeth.Venkatesh@arm.com]
> Sent: Monday, December 10, 2018 8:40 AM
> To: Jin, Eric <eric.jin@intel.com>; Leif Lindholm
> <leif.lindholm@linaro.org>; Kinney, Michael D
> <michael.d.kinney@intel.com>
> Cc: edk2-devel@lists.01.org; Dong Wei <Dong.Wei@arm.com>
> Subject: RE: SCT bugzilla topic?
>
> I guess we are in agreement that "EDK2-Test" product and "UEFI-SCT"
> component in Bugzilla  is required.
>
> Mike,
> Can you please help create this and let us know?
>
> Thanks,
> Supreeth
>
> -----Original Message-----
> From: Jin, Eric <eric.jin@intel.com>
> Sent: Monday, December 10, 2018 2:43 AM
> To: Leif Lindholm <leif.lindholm@linaro.org>; Kinney, Michael D
> <michael.d.kinney@intel.com>
> Cc: Supreeth Venkatesh <Supreeth.Venkatesh@arm.com>; edk2-
> devel@lists.01.org; Dong Wei <Dong.Wei@arm.com>
> Subject: RE: SCT bugzilla topic?
>
> Hi Leif,
>
> We had better use "UEFI SCT" as the component.
> Other SCTs or test suites may be arranged in the EDK2-Test in future
> as the intention of EDK2-Test if my understanding is correct. Thanks.
>
> Best Regards
> Eric
>
> -----Original Message-----
> From: Leif Lindholm <leif.lindholm@linaro.org>
> Sent: Monday, December 10, 2018 4:14 PM
> To: Kinney, Michael D <michael.d.kinney@intel.com>
> Cc: Jin, Eric <eric.jin@intel.com>; Supreeth Venkatesh
> <Supreeth.Venkatesh@arm.com>; edk2-devel@lists.01.org; Dong Wei
> <Dong.Wei@arm.com>
> Subject: Re: SCT bugzilla topic?
>
> Hi Mike,
>
> I think we're agreed on an "EDK2 Test" product with an "SCT"
> component.
> (Although that should probably be "UEFI SCT" for clarity.)
>
> Regards,
>
> Leif
>
> On Mon, Dec 10, 2018 at 03:02:57AM +0000, Kinney, Michael D wrote:
> > I can update BZ once there is a clear decision on what
> is required.
> >
> > Mike
> >
> > > -----Original Message-----
> > > From: Jin, Eric
> > > Sent: Sunday, December 9, 2018 6:19 PM
> > > To: Supreeth Venkatesh <Supreeth.Venkatesh@arm.com>;
> Leif Lindholm
> > > <leif.lindholm@linaro.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?
> > >
> > > 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.
> 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.
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 17:51 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
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 [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=AM4SPR01MB26941BE7454B2CE1130FF2A80A50@AM4SPR01MB269.eurprd08.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