we thought about this together with our Yocto team. the preffered way (as we already doing with SOF is to have a separate branch)
but having a tag i think can work for a while.
do we plan to do this for each SOF release, right?
zephyr development model looked a little bit different than SOF (I think they have some sort of LTS release every year and keep that for customers)
I think we'll do this for a while now. one recommendation from Zephyr folks for us to branch a stable release and cherry-pick patches SOF needs. we could host this in SOF github project (we already have a copy of zephyr there)
probably for all platforms, we'll need a pretty bleeding edge Zephyr in practise, so we'll probably need a few iterations before we can move to use a Zephyr LTS for SOF
I think that would be a good choice. Initially, I suggested to fork zephyr internally. but i think doing that on SOF github is better.
@kv2019i can you point me to the script you use the zephyr tagged version? I'm trying to integrate this internally now