lifecycle Release Note v0.8.0
|
status: valid
security: NO
safety: ASIL_B
|
||||
Release Note v0.8.0#
Overview#
This document provides an overview of the changes, improvements, and bug fixes included in the software module release version named above as compared to the module’s origin release (which is usually the previous release).
Disclaimer#
This release note does not “release for production”, as it does not come with a safety argumentation and a performed safety assessment. The work products compiled in the safety package are created with care according to a process satisfying standards, but the as the project, being a non-profit and open source organization, can not take over any liability for its content.
Changes to the Module#
New Features#
New ILmControl API that allows State Managers to communicate with Launch Manger using mw::com.
Improvements#
Unsupported configuration combinations are now detected at build time, and result in a build error: - A component with application_type Reporting only supports Running as the process state ready condition.
A warning is produced during build for the following scenarios: - If a ready condition is configured with the Terminated process state and a shutdown_timeout_ms is configured in deployment_config. The shutdown_timeout_ms will not have an effect.
Documentation with integration hints. - Added code examples. - Explanations of the mw::config config.
Bug Fixes#
None
Other Changes by Label#
None
Compatibility#
The following platforms are supported using the bazel_cpp_toolchains:
x86_64-unknown-linux-gnu
aarch64-unknown-linux-gnu
x86_64-unknown-nto-qnx800
aarch64-unknown-nto-qnx800
Performed Verification#
Build on all supported platforms
Unit test execution on all supported platforms
Known Issues#
None
Known Vulnerabilities#
None
Upgrade Instructions#
New ILmControl API is replacing the ControlClient please look at https://eclipse-score.github.io/lifecycle/main/components/launch_manager/product_documentation/integration.html#integration for instruction - Extended the execution_error.h with new errors to support this.
Config changes: - The top level fallback_run_target object is now mandatory through the schema. - number_of_attempts has a maxium of 255. - Configurations that combine application_type: Reporting with any process-state ready condition other than Running is now rejected.
For any questions or support, please contact the Project Team or raise an issue/discussion.