Platform Release Notes#
Note
Document header
Platform Release Note
|
status: draft
safety: ASIL_B
|
||||
Platform Name: [S-CORE]
Release Tag: v0.5.0
Origin Release Tag: none - first published release
Release Commit Hash: <add hash>
Release Date: YYYY-MM-DD
Overview
——–
This document provides an overview of the changes, improvements, and bug fixes included in the software platform release version v0.5.0
as compared to the platform origin release (which is usually the previous release).
New Features
————
- Inter-process Communication: Data transfer between processes on the same processor, based on shared memory.
- Fixed execution order framework: Provides fixed and deterministic computation of tasks for applications.
- Logging: Capturing detailed information about system events and application-level activities.
- Persistency Key-Value-Storage: Structured permanent data for applications.
Improvements
————
- none, first published release
Bug Fixes
———
- none, first published release
Integrated Software Modules
—————————
- Communication: (Version). Link to Software module release note.
- FEO: (Version). Link to Software module release note.
- Logging: (Version). Link to Software module release note.
- Tracing: (Version). Link to Software module release note.
- Baselibs: (Version). Link to Software module release note.
- OS: (Version). Link to Software module release note (external module).
- Persistency: (Version). Link to Software module release note.
Associated Infrastructure Modules
———————————
- process_description: (Version). Process description of S-CORE. Link to release note?
- docs-as-code: (Version). Tooling for linking and generation of documentation. Link to release note?
- tooling: (Version). Provided tooling for S-CORE development. Link to release note?
- itf: (Version). Integration Test Framework. Link to release note?
Performed Verification
———————-
This release note is based on the verification as documented in platform verification report
<need link to add>.
Known Issues
————
- Issue 1: Brief description of the known issue. Justification regarding safety impact.
- Issue 2: Brief description of the known issue. Justification regarding safety impact.
- Issue 3: Brief description of the known issue. Justification regarding safety impact.
Upgrade Instructions
——————–
1. none, first published release.
Contact Information
——————-
For any questions or support, please contact the Project lead or raise an issue/discussion.