lifecycle Release Note v0.4.0
status: valid
security: NO
safety: ASIL_B
version: 1

Release Note v0.4.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#

  • None

Improvements#

  • None

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#

  • Update include paths and BUILD labels for public mocks.
    • Rename all usage of //score/launch_manager:applicationcontext_mock_c to //score/launch_manager:mock_applicationcontext_cc.

    • Rename all usage of //score/launch_manager:lifecycle_mock_cc to //score/launch_manager:mock_lifecycle_cc.

    • Rename all usage of //score/launch_manager:report_running_mock_cc to //score/launch_manager:mock_lifecycle_cc.

    • Rename all usage of applicationcontextmock.h to mock_applicationcontext.h.

    • Rename all usage of lifecyclemanagermock.h to mock_lifecyclemanager.h.

    • Rename all usage of report_running_mock.h to mock_report_running.h.

    • These changes introduce a consistent naming convention for the test doubles in the lifecycle repository. More information in #422

  • Backward compatibility with the previous release is not guaranteed.

For any questions or support, please contact the Project Team or raise an issue/discussion.