Hi

A couple of questions, less technical than usual.

Do we have any sample cases of bringing boards back from older
branches? I would like to have a branch set up for bringing back some
selected AGESA from 4.18 branch. My plan would be to backport features
from ToT into said new branch and resolve issues there. Once
considered clean enough, it should be a three commit drop (vendorcode,
platform, boards) to land on master?
 
Sounds like a reasonable plan.
 
Is there someone (corporate) currently funding or hiring personnel
with reviews and tree maintenance as a priority? Is there currently
anyone actually assigning from their existing resources to put
attention to frameworks, while customers' board ports and resolving
their issues have tight schedules?

I'm willing to put in some time into reviewing this effort.

Arthur

On Tue, Apr 25, 2023 at 3:51 PM Kyösti Mälkki <kyosti.malkki@gmail.com> wrote:
Hi

A couple of questions, less technical than usual.

Do we have any sample cases of bringing boards back from older
branches? I would like to have a branch set up for bringing back some
selected AGESA from 4.18 branch. My plan would be to backport features
from ToT into said new branch and resolve issues there. Once
considered clean enough, it should be a three commit drop (vendorcode,
platform, boards) to land on master?

Is there someone (corporate) currently funding or hiring personnel
with reviews and tree maintenance as a priority? Is there currently
anyone actually assigning from their existing resources to put
attention to frameworks, while customers' board ports and resolving
their issues have tight schedules?


Regards,
Kyösti Mälkki
_______________________________________________
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-leave@coreboot.org