public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@bsdio.com>
To: Laszlo Ersek <lersek@redhat.com>,
	devel@edk2.groups.io, michael.d.kinney@intel.com
Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>,
	Andrew Fish <afish@apple.com>, Leif Lindholm <leif@nuviainc.com>,
	"Justen, Jordan L" <jordan.l.justen@intel.com>,
	Peter Grehan <grehan@freebsd.org>
Subject: Re: [edk2-devel] Where to put the bhyve code in the edk2 repo: BhyvePkg, or under OvmfPkg?
Date: Wed, 13 May 2020 20:34:42 -0600	[thread overview]
Message-ID: <764a2a86-6d80-9784-6793-e2a0cfe0a155@bsdio.com> (raw)
In-Reply-To: <2de7aa2e-a024-3c2b-14c0-161e68c31121@redhat.com>

(cc Peter Grehan)

On 5/12/20 3:28 AM, Laszlo Ersek wrote:

>
> If the bhyve community can *permanently* provide reviews /
> regression-testing for such OVMF contributors that never use bhyve, that
> would significantly increase the stability of bhyve firmware code, and
> it would outweigh bhyve's user base (likely) being smaller. Xen
> regressions were also reduced when the Xen community finally delegated
> designated reviewers to edk2.
>
> Reviewing and testing patches you don't really care for, but see as
> possibly regressive for the platform you do care about, is a *lot* of
> work. So I guess it could boil down to how much work your platform's
> user base can contribute to the edk2 project.

I certainly can't commit to reviewing and manually regression-testing 
all applicable OVMF patches, since I'm doing this on a volunteer basis 
and I know there will be days/weeks when my attention shifts elsewhere.

The best I could do is provide semi-regular testing and integration 
perhaps every month, and make available a permanent FreeBSD machine that 
any contributors/maintainers could remote into in order to do their own 
testing - in addition to providing integration into the CI system once 
.NET and Azure Agent support has been fixed on FreeBSD.


-- 

Rebecca Cran



  parent reply	other threads:[~2020-05-14  2:34 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08 15:44 Where to put the bhyve code in the edk2 repo: BhyvePkg, or under OvmfPkg? Rebecca Cran
2020-05-11 15:55 ` Laszlo Ersek
2020-05-11 16:20   ` Ard Biesheuvel
2020-05-11 16:36     ` Michael D Kinney
2020-05-11 16:38       ` Andrew Fish
2020-05-11 16:41         ` [edk2-devel] " Michael D Kinney
2020-05-11 21:12       ` Laszlo Ersek
2020-05-11 21:22         ` Michael D Kinney
2020-05-11 21:58           ` [edk2-devel] " Rebecca Cran
2020-05-12  9:28             ` Laszlo Ersek
2020-05-12  9:52               ` Ard Biesheuvel
2020-05-12 15:09                 ` Laszlo Ersek
2020-05-14  2:34               ` Rebecca Cran [this message]
2020-05-14 10:24                 ` Laszlo Ersek
2020-05-14 16:20                   ` Rebecca Cran
2020-05-14 17:48                     ` Sean
2020-05-14 18:22                       ` Rebecca Cran
2020-05-14 18:46                         ` Sean
2020-05-14 18:54                           ` Rebecca Cran
2020-05-15  9:39                       ` Laszlo Ersek
2020-05-15  9:42                     ` Laszlo Ersek
2020-05-15  9:47                       ` Ard Biesheuvel
2020-05-15 12:51                         ` Laszlo Ersek
2020-05-15 15:03                           ` Leif Lindholm
2020-05-11 16:25   ` 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=764a2a86-6d80-9784-6793-e2a0cfe0a155@bsdio.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