OEM archive plans for 22.04

Alex Tu alex.tu at canonical.com
Mon Jan 24 07:05:15 UTC 2022

Hi Lukasz,

Thanks for thinking of the OEM metas.
The OEM meta so far is mainly used to control the kernel favor.
We always upstream all needed fix during the enablement so ideally, 22.04
should just work well without OEM metas.

So far, the certification is based on LTS version:
My team will upload a new OEM meta if customers request a re-enablement on
22.04 with added new device support. (e.g. wifi, graphic card..etc)

On Mon, Jan 24, 2022 at 2:08 PM Shih-Yuan Lee (FourDollars) <
sylee at canonical.com> wrote:

> Hi Lukasz,
> CC Alex,
> Please correct me if I'm wrong.
> Lukasz Zemczak <lukasz.zemczak at canonical.com> 於 2022年1月18日 週二 下午10:35寫道:
>> Hello everyone,
>> With a few of my hats on (technical board, SRU, release team), as I
>> was diving into documenting some of the OEM archive portions, I
>> started thinking a bit more about the OEM situation for the incoming
>> 22.04 release. I was not part of any of the original discussions for
>> the OEM stack, so I'd be grateful for some knowledge sharing from
>> people that know more.
>> We introduced the OEM-specific metapackages in 20.04, enabling the OEM
>> archives for certain certified SKUs. This was limited only to 20.04.
>> Now, the next hot LTS is coming our way and I was wondering: what is
>> the plan there?
> The plan is to manually MIR OEM metapackages again when the Devices team
> works on the LTS+1 migration from 20.04 to 22.04.
> Basically, the goal of OEM metapackages is not to use OEM metapackage.
>> My main concern is that it was said that the meta packages should be
>> strictly for focal *only*, so none of the meta packages have been in
>> any devel release since then. Those were always going straight and
>> only to 20.04. Since 22.04 is an LTS, people running 20.04 will get
>> the ability to upgrade, so I'd like to make sure we have the upgrade
>> story straight.
> The OEM preloaded platforms will stick with 20.04 because the Devices team
> disabled the upgrade path by default. (Of course, the end users can enable
> it manually.)
> Devices team will enable the upgrade path again after all OEM preloaded
> platforms are verified to work fine on 22.04.
> During the verification period, Devices team may MIR some OEM metapackages
> again if they need some special customizations.
>> As said, I might be missing some context - maybe this has been
>> discussed already. But is the plan to get all the current oem-*-meta
>> packages no-change rebuilt for jammy? Or are those going to be
>> re-introduced as certification of machines for 22.04 goes forward?
> It should be re-introduced as certification of machines for 22.04.
> But oem-qemu-meta is OK to be rebuilt for jammy.
> oem-qemu-meta is a testing OEM metapackage.
> I will MIR some OEM metapackage for jammy just like
> oem-somerville-three-eyed-raven-meta for focal in the following days as a
> pilot run.
>> Cheers,
>> --
>> Łukasz 'sil2100' Zemczak
>>  Foundations Team
>>  lukasz.zemczak at canonical.com
>>  www.canonical.com
>> --
>> ubuntu-devel mailing list
>> ubuntu-devel at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
> Please let me know if you have any questions.
> --
> Shih-Yuan Lee (FourDollars) | Software Engineer | Delivery | Customer
> Engineering | Devices | Canonical
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20220124/f8d4c275/attachment.html>

More information about the ubuntu-devel mailing list