From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, spbrogan@outlook.com, lersek@redhat.com,
bob.c.feng@intel.com
Cc: Jordan Justen <jordan.l.justen@intel.com>,
Andrew Fish <afish@apple.com>, Ray Ni <ray.ni@intel.com>
Subject: Re: [edk2-devel] [Patch 1/1] EmulatorPkg/PlatformCI: stick with "ubuntu-18.04" for now
Date: Fri, 8 Jan 2021 11:14:06 -0700 [thread overview]
Message-ID: <05cac02b-c2e3-8cef-8795-59ce6d2a1c71@bsdio.com> (raw)
In-Reply-To: <DM6PR07MB718017C8F3C200334B00E28EC8AE0@DM6PR07MB7180.namprd07.prod.outlook.com>
On 1/8/21 11:01 AM, Sean wrote:
> Question to the community (especially those using a Linux environment)
> is what priority should it be to go resolve these and update CI to run
> on Ubuntu 20.04? General premise is we should stay current without
> being bleeding edge but I want to understand other perspectives.
From previous discussions, it sounds like we did want to be on the
bleeding edge - which I personally think is a bad idea, since breaking
changes can come in at the worst time.
Instead, we should stay on a stable release but watch out for newer
versions and move forward to them after applying any fixes.
--
Rebecca Cran
next prev parent reply other threads:[~2021-01-08 18:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 3:19 [Patch 1/1] EmulatorPkg/PlatformCI: stick with "ubuntu-18.04" for now Bob Feng
2020-12-21 13:47 ` [edk2-devel] " Laszlo Ersek
2020-12-21 14:05 ` Laszlo Ersek
2020-12-21 14:53 ` Laszlo Ersek
2020-12-22 0:04 ` Bob Feng
2021-01-08 18:01 ` Sean
2021-01-08 18:14 ` Rebecca Cran [this message]
2021-01-08 18:34 ` Laszlo Ersek
2021-01-08 18:54 ` Rebecca Cran
[not found] ` <1658569DBC96D253.25961@groups.io>
2021-01-08 20:20 ` Rebecca Cran
2021-01-11 8:24 ` Laszlo Ersek
2021-01-08 18:21 ` Laszlo Ersek
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=05cac02b-c2e3-8cef-8795-59ce6d2a1c71@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