Commit Graph

5 Commits

Author SHA1 Message Date
Kai Vehmanen a90435734e versions.json: set version to 2.9.99
Open tree for 2.10 development now that stable-v2.9 is branched out.

Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
2024-03-04 18:21:58 +02:00
Kai Vehmanen 5c0f8bdf6a versions.json: set version to 2.8.99
Open tree for 2.9 development now that stable-v2.8 is branched out.

Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
2023-11-27 16:49:43 +00:00
Kai Vehmanen 6ec4b611ef versions.json: version to 2.7.99
With stable-v2.7 branch create, set the mainline version
to 2.7.99 to prepare for SOF v2.8 development.

Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
2023-09-06 11:21:23 +03:00
Marc Herbert 212e9808a4 versions.json: bump to 2.6.99
Adopt Zephyr's (and others) .99 convention to indicate a development
branch.

Signed-off-by: Marc Herbert <marc.herbert@intel.com>
2023-06-07 18:26:26 +03:00
Marc Herbert 11592fed5b version.cmake: switch SOF_MAJOR etc. to a new, static `versions.json`
As discussed in #6952, relying on `git describe` for defining SOF_MAJOR
and friends is very brittle and unreliable. Switch to a static
versions.json file instead.

Note the full `git describe --tags` output is _still_ present in the
binary, this is useful and left unchanged. It's just not used any more
to guess SOF_MAJOR, SOF_MINOR and SOF_MICRO.

Use JSON because CMake and pretty much every other piece of software has
a JSON parser out of the box.

This aligns with linux/Makefile, Zephyr/VERSIONS and probably many
others. - except we use JSON because we're in 2023 so we don't spend
time having fun re-implementing parsers any more.

Signed-off-by: Marc Herbert <marc.herbert@intel.com>
2023-05-04 16:57:28 +03:00