[Q]: Release Strategy for Template Repository

[eriksven]

Question

Hello,

what is the plan for future releases of the Vehicle App Template? Will there be future releases or do you plan to rely more on the AppManifest?
For instance, to which version of the Python SDK should the template be compatible?
Since the latest template release 0.1.0 there have been multiple releases of the SDK (from 0.9.0 to 0.13.0).

For instance, the seat adjuster example references the seat adjuster example application in version 0.9.0. However, this code does not seem to work in the application container build with the content of the main-branch of the Eclipse Velocitas Template repository.

[kse3hi]

Hi @eriksven ,
We are trying to follow the semantic version rules, but it is complicated for such instances as templates.
Therefore at least the next statement shall be always true: "The latest template shall be compatible with the latest SDK".

While developing goes on active phase - we are not sure of compatibility between 0.?.? versions.

As far as we will release 1.0.0 version compatibility will be follow semantic version rules.

[eriksven]

Thanks for the answer, just to clarify, you therefore do not plan to do releases for the template repository soon?

[kse3hi]

Hi @eriksven , as for specific GitHub "template" functionality we consider each commit on main with reference HEAD on it as release - it means the latest main is always updated to the fresh state and released with each PR. As for the official Eclipse Release Process - it is currently in discussion.