On 11/28/23 12:56, Philipp Tomsich wrote:
That's obviously a risky thing to do given it was sent right at the end
of the window, but it meets the rules.
Folks in the call seemed generally amenable to at least trying for 14,
so unless anyone's opposed on the lists it seems like the way to go.
IIRC we ended up with the following TODO list:
* Make sure this doesn't regress on the targets we already support.
From the sounds of things there's been test suite runs that look fine,
so hopefully that's all manageable. Christoph said he'd send
something out, we've had a bunch of test skew so there might be a bit
lurking but it should be generally manageable.
* We agree on some sort of support lifecycle. There seemed to be
basically two proposals: merge for 14 with the aim of quickly
deperecating it (maybe even for 15), or merge for 14 with the aim of
keeping it until it ends up un-tested (ie, requiring test results are
published for every release).
We expect real-world users, including the BeagleV-AHEAD community, to
need support for the foreseeable future.
Keeping it until it ends up untested (and test cases are reasonably
clean) sounds like a good threshold to ensure the integrity of the
codebase while giving this a clear path to stay in for its useful
life.
I can live with it being in the tree as long as it's maintained
(measured by ongoing testing with reasonable results).
I'd proposed that it could end up deprecated quickly, but that was based
on the assumption that once V1.0 compliant hardware was widely available
that we'd see less and less interest in the thead extensions.
Jeff
