> We could announce this deprecation in the 4.16 release notes, then deprecate after 4.18 (8.5 months from now). At that point, we'd create a branch and set up a verification builder so that any deprecated platforms could be continued in the 4.18 branch.
That timeline of 8.5 months does sound fair. I just found this updated release schedule in the meeting minutes. If we are going to release every 3 months then I guess that's a good way to go. I started a CL: https://review.coreboot.org/c/coreboot/+/59618 . I'll update it to reflect that schedule if it can be agreed upon. On Wed, Nov 24, 2021 at 6:07 PM Martin Roth <[email protected]> wrote: > Hey Arthur, > > Nov 24, 2021, 05:50 by [email protected]: > > > Hi > > I would like to suggest to deprecate some legacy codepaths inside the > coreboot tree and therefore make some newer ones mandatory. > > ... snip ...> About the timeline of deprecations. Is deprecating non > conforming platforms from the master branch after the 4.16 release in 6 > months a reasonable proposal? > > > I have no strong opinion about the platform deprecations, although I > suspect that PC Engines might be unhappy if it's platforms were removed > from the ToT codebase. > > My preference would be to announce deprecations in the release notes. We > just missed the 4.15 release, but we're switching to a 3 month release > cadence, so the next release will be in early February, 2.5 months from now. > > We could announce this deprecation in the 4.16 release notes, then > deprecate after 4.18 (8.5 months from now). At that point, we'd create a > branch and set up a verification builder so that any deprecated platforms > could be continued in the 4.18 branch. > > Would this schedule work? > > Martin > >
_______________________________________________ coreboot mailing list -- [email protected] To unsubscribe send an email to [email protected]
