Closed kowend closed 3 months ago
Topics to discuss:
I think marking them as deprecated is fine, and leave them in. Is there any standard/rule for removing deprecations? I can imagine we don't want too many deprecations left in the specs.
For which version would these signals then be deprecated?
Ah nevermind about the rule for deprecation. I found the description in the basics.md. But knowing the version for deprecation would still be useful. Would that be v5.0?
Ah nevermind about the rule for deprecation. I found the description in the basics.md. But knowing the version for deprecation would still be useful. Would that be v5.0?
Possibly. Historically we have selected "next release" as "deprecated from", but right now we have not really decided if we will release a 4.2 or if next release will be 5.0. I would say that 5.0 is the best option for now for main, if we decide to create a 4.2 then we as maintainers should anyway check all deprecation comments and adjust version if needed, like replacing 5.0 with 4.2 for the maintenance branch.
Clear! I'll add the deprecation attributes. I've realised that the electrical motor could also have a cooling compartiment. At least the coolant temperature is mentioned as an optional. I've moved the coolant branch into a separate spec file.
MoM:
MoM:
MoM:
MoM:
I have no further comments. I am fine with the responses that were provided, with a note that I am still slightly in favour of reusing the set of enum values, but not enough to block merge.
MoM:
Several engine oil and coolant related attributes where spread in the main branch of the combustion engine. The engine oil and coolant have been put under a branch. Additional coolant lifespan and level (ISO 7000 2429) have been added under the coolant branch.