Add compatibility test #337
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ppb2020
reviewed
Mar 27, 2024
README.md
Outdated
| @@ -42,6 +42,30 @@ Examples on tool usage can be found in the [VSS Makefile](https://github.com/COV | |||
|
|
|||
| All current tools are based on common Python functionality in the `vspec` folder to read, parse and expand a Vehicle Signal Specification files(*.vspec files). As an example, if the standard [VSS root file](https://github.com/COVESA/vehicle_signal_specification/blob/master/spec/VehicleSignalSpecification.vspec) is given as input then the Python tooling will read all included files, do a validation of the content, expand any instances used and create an in-memory representation which then can be used by specialized tools to generate the wanted output. | |||
|
|
|||
| ## Compatibility with VSS | |||
|
|
|||
| The [COVESA VSS project repository](https://github.com/COVESA/vehicle_signal_specification) include vss-tools as a submodule. | |||
README.md
Outdated
| ## Compatibility with VSS | ||
|
|
||
| The [COVESA VSS project repository](https://github.com/COVESA/vehicle_signal_specification) include vss-tools as a submodule. | ||
| The vss-tools version linked by the VSS repository is the preferred vss-tools version to use for that particular version of the VSS repository. It is not guaranteed that newer or older versions of vss-tools successfully can handle that particular version of the VSS repository. The table below gives an overview of basic version support, |
There was a problem hiding this comment.
successfully can -> can successfully
| # | ||
| # Intended workflow: | ||
| # | ||
| # ---------- After a new VSS release ----------------- |
There was a problem hiding this comment.
How do we remember to come update this for every release?
There was a problem hiding this comment.
What we could do is to mention it in:
https://github.com/COVESA/vss-tools/wiki/Release-Instructions-and-Checklist
https://github.com/COVESA/vehicle_signal_specification/wiki/Release-Instructions-and-Checklist
I.e. update it as part of release preparation.
erikbosch
force-pushed
the
erik_compat
branch
2 times, most recently
from
4141518 to
8dc1c99
Compare
|
MoM:
|
Signed-off-by: Erik Jaegervall <erik.jaegervall@se.bosch.com>
|
MoM: Merge |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This intends to make us more conscious on if we break backward compatibility, so that we can take a deliberate decision if that is OK and possibly could document it as well.