public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: Supreeth Venkatesh <Supreeth.Venkatesh@arm.com>,
	"edk2-devel@lists.01.org (edk2-devel@ml01.01.org)"
	<edk2-devel@ml01.01.org>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-staging] Create new edk2-test branch
Date: Thu, 26 Jan 2017 17:54:46 +0000	[thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5648AC456@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <HE1PR0802MB23167EFEEEA15C5B14A67A3480770@HE1PR0802MB2316.eurprd08.prod.outlook.com>

Supreeth,

Thanks!  I will add you as one of the owner's in the Readme.md.

We use the same edk2 patch method and use the same edk2-devel mailing
list. The only difference is the format of the subject line so everyone
can clearly identify staging topics from edk2 topics.  For work on the 
edk2-test branch, the subject line format would be:

	[staging/edk2-test PATCH] Package/Module: <Brief Description>

Additional details on the edk2-staging development process can be
found at:

	https://github.com/tianocore/edk2-staging/tree/about

We can also use Bugzilla to track features and bug fixes for edk2-test.

	https://bugzilla.tianocore.org/

I may need to do some minor updates to Bugzilla so staging features and
bugs are separated from edk2 features and bugs.
	
Best regards,

Mike

> -----Original Message-----
> From: Supreeth Venkatesh [mailto:Supreeth.Venkatesh@arm.com]
> Sent: Thursday, January 26, 2017 9:12 AM
> To: Kinney, Michael D <michael.d.kinney@intel.com>; edk2-devel@lists.01.org
> (edk2-devel@ml01.01.org) <edk2-devel@ml01.01.org>
> Subject: RE: [edk2-staging] Create new edk2-test branch
> 
> Michael,
> 
> I am interested in developing the test harness and /or the test case SDK.
> Should the contribution to this, when it is still in Staging, should it follow
> edk2 patch methodology or do you have a separate email alias for edk2-test
> related queries/patches?
> 
> Thanks,
> Supreeth
> 
> 
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Kinney,
> Michael D
> Sent: Wednesday, January 25, 2017 1:07 AM
> To: edk2-devel@lists.01.org (edk2-devel@ml01.01.org); Kinney, Michael D
> Subject: [edk2] [edk2-staging] Create new edk2-test branch
> 
> I am creating a new branch in edk2-staging called edk2-test.
> 
> The purpose of this branch is to develop a test harness, test case SDK, and
> library of test cases that can be used as part of edk2 validation.
> 
> The initial version of this test harness is compatible with binary releases of
> the PI SCTs and UEFI SCTs, are native
> edk2 packages with no dependencies on the EdkCompatibilityPkg, and the test
> harness runs using the latest version of the UEFI Shell.
> 
> Additional work items:
> * Update to take advantage of latest edk2 features/libraries.
> * Update for all supported CPU types
> * Update for all supported compilers
> * Review initial test harness features and determine
>   what features should be dropped and what new features
>   should be added.
> * Determine where the test harness, test case SDK, and
>   test cases should live once the initial functional and
>   quality criteria are met.  Could be packages in the
>   edk2 repo or packages in a new edk2-test repo.  Other
>   options???
> * Resolve compatibility issues with binary releases of the
>   PI SCTs and UEFI SCTs.
> * Update test harness to support PEI tests
> * Update test harness to support Runtime tests
> * Update test harness to support SMM tests
> * Optimize performance of the test harness and tests.
> 
> Please contact me if you are interested in helping with the test harness, the
> test case SDK, or the development of test cases.
> 
> Thanks,
> 
> Mike
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
> 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:[~2017-01-26 17:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25  7:07 [edk2-staging] Create new edk2-test branch Kinney, Michael D
2017-01-25 22:05 ` Kinney, Michael D
2017-01-26  9:57   ` Andrew Fish
2017-01-26 14:15     ` Rudra ठाकुर
2017-01-26 17:56       ` Kinney, Michael D
2017-01-26 17:43     ` Kinney, Michael D
2017-01-26 18:25       ` Andrew Fish
2017-01-26 19:36         ` Kinney, Michael D
2017-01-26 19:37           ` Andrew Fish
2017-01-26 19:39             ` Andrew Fish
2017-01-26 17:11 ` Supreeth Venkatesh
2017-01-26 17:54   ` Kinney, Michael D [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=E92EE9817A31E24EB0585FDF735412F5648AC456@ORSMSX113.amr.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