versions.json: set version to 2.8.99

[kv2019i]

Open tree for 2.9 development now that stable-v2.8 is branched out.

[lgirdwood]

@wszypelt @lrudyX fyi - version bump should not be tested by CI ?

[lrudyX]

@wszypelt @lrudyX fyi - version bump should not be tested by CI ?

There are no special tests for version bumps, but we check this on daily /weekly scopes. This is not CI blocker. Thank you for this attention.

[lgirdwood]

@wszypelt @lrudyX fyi - version bump should not be tested by CI ?

There are no special tests for version bumps, but we check this on daily /weekly scopes. This is not CI blocker. Thank you for this attention.

and I assume we are good to merge ?

[lrudyX]

@wszypelt @lrudyX fyi - version bump should not be tested by CI ?

There are no special tests for version bumps, but we check this on daily /weekly scopes. This is not CI blocker. Thank you for this attention.

and I assume we are good to merge ?

Yes, that is correct.

[kv2019i]

Btw, @marc-hb , should we tag the branch points. Now the main branch doesn't have the release tags. We bake git-based versions into the binary, and now SOF main looks like

[    0.304501] <inf> init: print_version_banner: FW ABI 0x301d000 DBG ABI 0x5003000 tags SOF:v2.5-stable-branch-1754-g5c0f8bdf6aea zephyr:zephyr-v3.5.0-2238-g18cb2004d1da src hash 0xbb6732f5 (ref hash 0xbb6732f5)

... which is quite misleading. I did "v2.5-stable-branch" , but this is not a convetion we have followed systematically. Maybe we should and tag the opening up of the main branch with "2.8.99" perhaps. Thoughts?

[marc-hb]

Probably yes.

This was already discussed in:

• How do we use tags on master branch? #3730