lifecycle Release Note v0.7.0
status: valid
security: NO
safety: ASIL_B
version: 1
realizes: wp__module_sw_release_note
doc__lifecycle_release_note_v0_7_0
Generic Document

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

  • All timing values in the configuration have been changed from unit seconds to unit milliseconds #637. See upgrade instructions below

  • All threads in launch_manager now have a name #631.

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#

  • Adapt the names and values for timing configuration. All timing values are now configured in milliseconds instead of seconds. #637 The following fields are impacted:

    • reporting_cycle -> reporting_cycle_ms

    • polling_interval -> polling_interval_ms

    • delay_before_restart -> delay_before_restart_ms

    • ready_timeout -> ready_timeout_ms

    • shutdown_timeout -> shutdown_timeout_ms

    • transition_timeout -> transition_timeout_ms

    • evaluation_cycle -> evaluation_cycle_ms

    • max_timeout -> max_timeout_ms

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