From 9ea71bfc5f4ec815480e5c8cac800c20ff56291c Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Thu, 13 Nov 2025 12:08:32 +0100 Subject: [PATCH 01/15] add some basic descriptions of some chapters --- docs/features/index.rst | 4 ++++ docs/modules/index.rst | 4 ++-- docs/requirements/index.rst | 4 ++++ docs/score_releases/index.rst | 5 +++++ 4 files changed, 15 insertions(+), 2 deletions(-) diff --git a/docs/features/index.rst b/docs/features/index.rst index 086c37767e9..d2dbfb42d93 100644 --- a/docs/features/index.rst +++ b/docs/features/index.rst @@ -17,6 +17,10 @@ Features ======== +A **Feature** is the highest-level logical entity, representing a complete, end-user or system-relevant functionality of the middleware or the vehicle. It is the primary unit of deployment, management, and business value. For further explanation see the `Building blocks concept `_. + +The following features are defined: + .. toctree:: :maxdepth: 1 :glob: diff --git a/docs/modules/index.rst b/docs/modules/index.rst index 5b67d461d77..ed8d2de1adb 100644 --- a/docs/modules/index.rst +++ b/docs/modules/index.rst @@ -17,6 +17,8 @@ Modules ======= +A **Module** is a major architectural building block that realizes a part of a Feature's logic. For further explanation see the `Building blocks concept `_. + .. image:: _assets/module_architecture.drawio.svg :alt: Module Architecture @@ -25,8 +27,6 @@ Modules For now, we store the modules documentation in the modules tree, because multi-repo docs are not yet supported. Once this support becomes available it will be moved to the right repo. - - .. toctree:: :maxdepth: 1 :glob: diff --git a/docs/requirements/index.rst b/docs/requirements/index.rst index 9e48d6c3f60..7f1f23ef671 100644 --- a/docs/requirements/index.rst +++ b/docs/requirements/index.rst @@ -17,6 +17,10 @@ Requirements ============ +Requirements are the formal descriptions of the requested capabilities or characteristics that the system or one of its components must fulfill. + +The following stakeholder functional and non-functional requirements and platform assumptions describe that for S-Core. + .. toctree:: stakeholder/index diff --git a/docs/score_releases/index.rst b/docs/score_releases/index.rst index 769ab115c54..2bde7b9361a 100644 --- a/docs/score_releases/index.rst +++ b/docs/score_releases/index.rst @@ -14,6 +14,11 @@ .. _releases: +S-CORE Releases +=============== + +A **Release** is an officially distributed, versioned, and deployable collection of software. It relates to a feature- (set of available features) and system-release (a software package comprising a defined set of Features and the underlying S-Core platform software). + S-CORE Releases Overview ======================== From 52a913830e079334d24dc63bd6a54b178307354e Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Thu, 13 Nov 2025 13:35:06 +0100 Subject: [PATCH 02/15] work on review findings --- docs/features/index.rst | 2 +- docs/requirements/index.rst | 2 +- docs/score_releases/index.rst | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/features/index.rst b/docs/features/index.rst index d2dbfb42d93..1f586883dc0 100644 --- a/docs/features/index.rst +++ b/docs/features/index.rst @@ -17,7 +17,7 @@ Features ======== -A **Feature** is the highest-level logical entity, representing a complete, end-user or system-relevant functionality of the middleware or the vehicle. It is the primary unit of deployment, management, and business value. For further explanation see the `Building blocks concept `_. +A **Feature** is the highest-level logical entity, representing a complete functionality in respect of the S-Core SW-platform. It is the primary unit of deployment, management, and business value. For further explanation see the `Building blocks concept `_. The following features are defined: diff --git a/docs/requirements/index.rst b/docs/requirements/index.rst index 7f1f23ef671..634ab16fb8c 100644 --- a/docs/requirements/index.rst +++ b/docs/requirements/index.rst @@ -17,7 +17,7 @@ Requirements ============ -Requirements are the formal descriptions of the requested capabilities or characteristics that the system or one of its components must fulfill. +Requirements are the formal descriptions of the requested capabilities or characteristics that the software platform or one of its components must fulfill. The following stakeholder functional and non-functional requirements and platform assumptions describe that for S-Core. diff --git a/docs/score_releases/index.rst b/docs/score_releases/index.rst index 2bde7b9361a..0c87b8ed1d7 100644 --- a/docs/score_releases/index.rst +++ b/docs/score_releases/index.rst @@ -17,7 +17,7 @@ S-CORE Releases =============== -A **Release** is an officially distributed, versioned, and deployable collection of software. It relates to a feature- (set of available features) and system-release (a software package comprising a defined set of Features and the underlying S-Core platform software). +A **Release** is an officially distributed, versioned, and deployable collection of the software platform. It relates to a feature- (set of available features) and software-release (a software package comprising a defined set of Features and the underlying S-Core platform software). S-CORE Releases Overview ======================== From b73b3ddae6fe4f86d268654d24d79bf9fe5c5ed7 Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Fri, 14 Nov 2025 07:38:50 +0000 Subject: [PATCH 03/15] correct descition after discussions --- docs/features/index.rst | 2 +- docs/modules/index.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/features/index.rst b/docs/features/index.rst index 1f586883dc0..cc6014c3074 100644 --- a/docs/features/index.rst +++ b/docs/features/index.rst @@ -17,7 +17,7 @@ Features ======== -A **Feature** is the highest-level logical entity, representing a complete functionality in respect of the S-Core SW-platform. It is the primary unit of deployment, management, and business value. For further explanation see the `Building blocks concept `_. +A **Feature** is the highest-level logical entity, representing a set of interrelated components in respect of the S-Core SW-platform. It is the primary unit of the management of these components and contains the belonging requirements and architecture for them. For further explanation see the `Building blocks concept `_. The following features are defined: diff --git a/docs/modules/index.rst b/docs/modules/index.rst index ed8d2de1adb..952b5108a28 100644 --- a/docs/modules/index.rst +++ b/docs/modules/index.rst @@ -17,7 +17,7 @@ Modules ======= -A **Module** is a major architectural building block that realizes a part of a Feature's logic. For further explanation see the `Building blocks concept `_. +A **Module** is a major architectural building block that packages one or more logically related Components. It is the physically compiled and packaged unit that results from the build process and is made available for delivery. For further explanation see the `Building blocks concept `_. .. image:: _assets/module_architecture.drawio.svg :alt: Module Architecture From 8c63bef6d52e722a1db4d04e6c8ec417e74df273 Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Fri, 14 Nov 2025 10:32:39 +0000 Subject: [PATCH 04/15] fix further review findings --- docs/features/index.rst | 2 +- docs/score_releases/index.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/features/index.rst b/docs/features/index.rst index cc6014c3074..9b8ac34f51a 100644 --- a/docs/features/index.rst +++ b/docs/features/index.rst @@ -17,7 +17,7 @@ Features ======== -A **Feature** is the highest-level logical entity, representing a set of interrelated components in respect of the S-Core SW-platform. It is the primary unit of the management of these components and contains the belonging requirements and architecture for them. For further explanation see the `Building blocks concept `_. +A **Feature** is the highest-level logical entity, representing a set of interrelated components in respect of the S-Core software platform. It is the primary unit of the management of these components and contains the belonging feature requirements and feature architecture for them. For further explanation see the `Building blocks concept `_. The following features are defined: diff --git a/docs/score_releases/index.rst b/docs/score_releases/index.rst index 0c87b8ed1d7..7a02229fe81 100644 --- a/docs/score_releases/index.rst +++ b/docs/score_releases/index.rst @@ -17,7 +17,7 @@ S-CORE Releases =============== -A **Release** is an officially distributed, versioned, and deployable collection of the software platform. It relates to a feature- (set of available features) and software-release (a software package comprising a defined set of Features and the underlying S-Core platform software). +A **Release** is an officially distributed, versioned, and deployable collection of the software platform. It relates to a collection of features and modules of the SW platform. For further information about the platform releases and module releases see `release documentation `_ in the process description. S-CORE Releases Overview ======================== From fd606f57de4a046f7a0d0710b9b7ad3c54889874 Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Fri, 14 Nov 2025 12:19:13 +0000 Subject: [PATCH 05/15] enhance requirement section --- docs/requirements/index.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/requirements/index.rst b/docs/requirements/index.rst index 634ab16fb8c..0c2f8276b44 100644 --- a/docs/requirements/index.rst +++ b/docs/requirements/index.rst @@ -17,7 +17,7 @@ Requirements ============ -Requirements are the formal descriptions of the requested capabilities or characteristics that the software platform or one of its components must fulfill. +Requirements are the formal descriptions of the requested capabilities or characteristics that the software platform or its components must fulfill. The feature requirements are derived from standards like ISO 26262 Part-8 and ASPICE and additionally includes requirements of the different stakeholders. For further information see the `requirement concept `_ in the process description. The following stakeholder functional and non-functional requirements and platform assumptions describe that for S-Core. From 66c3b84406d6e22b6df5c01b5eb56c872b1e03cf Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Fri, 14 Nov 2025 12:20:15 +0000 Subject: [PATCH 06/15] enhance requirement section --- docs/requirements/index.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/requirements/index.rst b/docs/requirements/index.rst index 0c2f8276b44..24536c34bd9 100644 --- a/docs/requirements/index.rst +++ b/docs/requirements/index.rst @@ -17,7 +17,7 @@ Requirements ============ -Requirements are the formal descriptions of the requested capabilities or characteristics that the software platform or its components must fulfill. The feature requirements are derived from standards like ISO 26262 Part-8 and ASPICE and additionally includes requirements of the different stakeholders. For further information see the `requirement concept `_ in the process description. +Requirements are the formal descriptions of the requested capabilities or characteristics that the software platform or its components must fulfill. The feature requirements are derived from standards like ISO 26262 Part-8 and ASPICE4 and additionally includes requirements of the different stakeholders. For further information see the `requirement concept `_ in the process description. The following stakeholder functional and non-functional requirements and platform assumptions describe that for S-Core. From 678c174bb870ff3304eba977c1800c9fd3364c6b Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Thu, 20 Nov 2025 08:08:15 +0000 Subject: [PATCH 07/15] correct module explanation --- docs/modules/index.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/modules/index.rst b/docs/modules/index.rst index 952b5108a28..4def14a6e28 100644 --- a/docs/modules/index.rst +++ b/docs/modules/index.rst @@ -17,7 +17,7 @@ Modules ======= -A **Module** is a major architectural building block that packages one or more logically related Components. It is the physically compiled and packaged unit that results from the build process and is made available for delivery. For further explanation see the `Building blocks concept `_. +A **Module** is a major architectural building block which is defined as a component or a set of components realizing a feature of the platform. It is the physically compiled and packaged unit that results from the build process and is made available for delivery. For further explanation see the `Building blocks concept `_. .. image:: _assets/module_architecture.drawio.svg :alt: Module Architecture From 329f2a639616044c87f8aeac4d9f62db8e270b31 Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Thu, 20 Nov 2025 08:45:48 +0000 Subject: [PATCH 08/15] add link to feature section --- docs/modules/index.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/modules/index.rst b/docs/modules/index.rst index 4def14a6e28..9949b019c7d 100644 --- a/docs/modules/index.rst +++ b/docs/modules/index.rst @@ -17,7 +17,8 @@ Modules ======= -A **Module** is a major architectural building block which is defined as a component or a set of components realizing a feature of the platform. It is the physically compiled and packaged unit that results from the build process and is made available for delivery. For further explanation see the `Building blocks concept `_. +A **Module** is a major architectural building block which is defined as a component or a set of components realizing a :ref:`feature ` of the platform. +It is the physically compiled and packaged unit that results from the build process and is made available for delivery. For further explanation see the `Building blocks concept `_. .. image:: _assets/module_architecture.drawio.svg :alt: Module Architecture From d7c72aa1b3b16b4744638cfd5eaa3fe521b7ae87 Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Thu, 20 Nov 2025 15:15:39 +0000 Subject: [PATCH 09/15] remove feature requirements description --- docs/requirements/index.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/requirements/index.rst b/docs/requirements/index.rst index 24536c34bd9..2fc2f115afd 100644 --- a/docs/requirements/index.rst +++ b/docs/requirements/index.rst @@ -17,7 +17,7 @@ Requirements ============ -Requirements are the formal descriptions of the requested capabilities or characteristics that the software platform or its components must fulfill. The feature requirements are derived from standards like ISO 26262 Part-8 and ASPICE4 and additionally includes requirements of the different stakeholders. For further information see the `requirement concept `_ in the process description. +Requirements are the formal descriptions of the requested capabilities or characteristics that the software platform or its components must fulfill. For further information see the `requirement concept `_ in the process description. The following stakeholder functional and non-functional requirements and platform assumptions describe that for S-Core. From 1faece9c5ca7def4009e52d02bc213ac2c279671 Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Fri, 21 Nov 2025 09:16:51 +0000 Subject: [PATCH 10/15] spelling for S-CORE --- docs/features/index.rst | 2 +- docs/platform_management_plan/project_management.rst | 6 +++--- docs/platform_management_plan/software_verification.rst | 4 ++-- docs/requirements/index.rst | 2 +- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/features/index.rst b/docs/features/index.rst index 9b8ac34f51a..08fe4d199f0 100644 --- a/docs/features/index.rst +++ b/docs/features/index.rst @@ -17,7 +17,7 @@ Features ======== -A **Feature** is the highest-level logical entity, representing a set of interrelated components in respect of the S-Core software platform. It is the primary unit of the management of these components and contains the belonging feature requirements and feature architecture for them. For further explanation see the `Building blocks concept `_. +A **Feature** is the highest-level logical entity, representing a set of interrelated components in respect of the S-CORE software platform. It is the primary unit of the management of these components and contains the belonging feature requirements and feature architecture for them. For further explanation see the `Building blocks concept `_. The following features are defined: diff --git a/docs/platform_management_plan/project_management.rst b/docs/platform_management_plan/project_management.rst index ef5c0c3fa63..5dc40f091ca 100644 --- a/docs/platform_management_plan/project_management.rst +++ b/docs/platform_management_plan/project_management.rst @@ -130,13 +130,13 @@ Its current *DoD list* is always documented in the template. The most important Every *Feature Team* should have its own discussion section in the `Feature Teams section `_ of the main *S-CORE* project. -* **Adding a new Team to the main S-Core GitHub project** +* **Adding a new Team to the main S-CORE GitHub project** Every *Feature Team* should be added as a further select option of the "Team" field - in the `main S-Core project `_, so that *Technical Leads* + in the `main S-CORE project `_, so that *Technical Leads* can assign tickets to the team and filter for the tickets of the new team. Additionally, every team is free to create its own GitHub project, but then the team tickets should be still - visible in the main S-Core project. + visible in the main S-CORE project. * **Creation of repository** diff --git a/docs/platform_management_plan/software_verification.rst b/docs/platform_management_plan/software_verification.rst index 60c1c391f5b..870615ac601 100644 --- a/docs/platform_management_plan/software_verification.rst +++ b/docs/platform_management_plan/software_verification.rst @@ -126,10 +126,10 @@ There are the following different levels of integration and verification defined **Note:** These three levels translate to the levels of ISO 26262 part 6 clauses 9 to 11. The platform - testing will be executed by the integrator. S-Core project only executes tests on reference hardware. + testing will be executed by the integrator. S-CORE project only executes tests on reference hardware. These tests serve as an optional base for the integrator and will also be part of the :need:`wp__verification_platform_ver_report`, but more on an informative character. The full scope - of clause 11 is tailored out accordingly for S-Core. Practically, this means S-CORE will implement + of clause 11 is tailored out accordingly for S-CORE. Practically, this means S-CORE will implement platform test of stakeholder requirements for demonstration, but these are not intended to completely covering all stakeholder requirements. diff --git a/docs/requirements/index.rst b/docs/requirements/index.rst index 2fc2f115afd..e12b299c7da 100644 --- a/docs/requirements/index.rst +++ b/docs/requirements/index.rst @@ -19,7 +19,7 @@ Requirements Requirements are the formal descriptions of the requested capabilities or characteristics that the software platform or its components must fulfill. For further information see the `requirement concept `_ in the process description. -The following stakeholder functional and non-functional requirements and platform assumptions describe that for S-Core. +The following stakeholder functional and non-functional requirements and platform assumptions describe that for S-CORE. .. toctree:: From df14d7429e2518b62e25563dda44683a0020d0d6 Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Fri, 21 Nov 2025 09:17:13 +0000 Subject: [PATCH 11/15] spelling for S-CORE --- docs/features/analysis-infra/logging/docs/glossary.rst | 4 ++-- docs/features/lifecycle/architecture/launch_manager.rst | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/features/analysis-infra/logging/docs/glossary.rst b/docs/features/analysis-infra/logging/docs/glossary.rst index 90647d8db52..dc146bc4127 100644 --- a/docs/features/analysis-infra/logging/docs/glossary.rst +++ b/docs/features/analysis-infra/logging/docs/glossary.rst @@ -26,10 +26,10 @@ Glossary Framework is a structured and extensible foundation for developing specific types of functionality in this case, logging. It supplies a set of default behaviors and configurable options, allowing developers to tailor and extend its capabilities to meet their application and system need. platform - Platform is the execution environment on which S-Core runs. It includes, for example, hardware (HW), operating system (OS), ... + Platform is the execution environment on which S-CORE runs. It includes, for example, hardware (HW), operating system (OS), ... component - Component is a S-Core component + Component is a S-CORE component log level Log Level is the severity of a log message, necessary to categorize logs based on their importance e.g., FATAL, ERROR, WARN, INFO, DEBUG, VERBOSE such as in DLT diff --git a/docs/features/lifecycle/architecture/launch_manager.rst b/docs/features/lifecycle/architecture/launch_manager.rst index 670c6e8f3b9..4c29c258d78 100644 --- a/docs/features/lifecycle/architecture/launch_manager.rst +++ b/docs/features/lifecycle/architecture/launch_manager.rst @@ -21,7 +21,7 @@ monitoring, and controlling processes based on defined configurations and requirements. As such, it is a central part of the lifecycle management in S-CORE and knows about the state of all processes in the system. -It's foreseen ECU projects will need a custom state management to fulfill ECU-project specific requirements. The S-Core stack will offer a framework to control application lifecycle, but will not specify the State Manager. +It's foreseen ECU projects will need a custom state management to fulfill ECU-project specific requirements. The S-CORE stack will offer a framework to control application lifecycle, but will not specify the State Manager. Overview ======== From f26c78e5af10d1a1a91c89f4118c55c0632690cb Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Mon, 24 Nov 2025 07:12:47 +0000 Subject: [PATCH 12/15] takeover of definition of releases --- docs/score_releases/index.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/score_releases/index.rst b/docs/score_releases/index.rst index 7a02229fe81..9cf598561ed 100644 --- a/docs/score_releases/index.rst +++ b/docs/score_releases/index.rst @@ -17,7 +17,7 @@ S-CORE Releases =============== -A **Release** is an officially distributed, versioned, and deployable collection of the software platform. It relates to a collection of features and modules of the SW platform. For further information about the platform releases and module releases see `release documentation `_ in the process description. +A **Release** is a crucial aspects of the project life cycle within the `Eclipse Development Process `_. It is a officially distributed, versioned, and deployable collection of Project artifacts intended for distribution beyond the Project Developers. It brings together the initial set of core modules, reference integrations, and supporting infrastructure needed to build. For further information about the platform releases and module releases see `release documentation `_ in the process description. S-CORE Releases Overview ======================== From 161f4300e3706ac4908950948c8e10746e328714 Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Mon, 24 Nov 2025 07:20:54 +0000 Subject: [PATCH 13/15] merge changes --- docs/platform_management_plan/software_verification.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platform_management_plan/software_verification.rst b/docs/platform_management_plan/software_verification.rst index 870615ac601..ca7fbf69a5b 100644 --- a/docs/platform_management_plan/software_verification.rst +++ b/docs/platform_management_plan/software_verification.rst @@ -130,7 +130,7 @@ There are the following different levels of integration and verification defined These tests serve as an optional base for the integrator and will also be part of the :need:`wp__verification_platform_ver_report`, but more on an informative character. The full scope of clause 11 is tailored out accordingly for S-CORE. Practically, this means S-CORE will implement - platform test of stakeholder requirements for demonstration, but these are not intended to completely + Platform Integration Test of stakeholder requirements for demonstration, but these are not intended to completely covering all stakeholder requirements. Verification Methods From 3c2d2d9c840ab79e42e998631ce95cdb2a52c450 Mon Sep 17 00:00:00 2001 From: RolandJentschETAS <135332348+RolandJentschETAS@users.noreply.github.com> Date: Mon, 24 Nov 2025 09:09:09 +0100 Subject: [PATCH 14/15] Update docs/requirements/index.rst Co-authored-by: Philipp Ahmann <2428012+pahmann@users.noreply.github.com> Signed-off-by: RolandJentschETAS <135332348+RolandJentschETAS@users.noreply.github.com> --- docs/requirements/index.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/requirements/index.rst b/docs/requirements/index.rst index e12b299c7da..0bf6aee5b54 100644 --- a/docs/requirements/index.rst +++ b/docs/requirements/index.rst @@ -19,7 +19,7 @@ Requirements Requirements are the formal descriptions of the requested capabilities or characteristics that the software platform or its components must fulfill. For further information see the `requirement concept `_ in the process description. -The following stakeholder functional and non-functional requirements and platform assumptions describe that for S-CORE. +The following stakeholder functional and non-functional requirements and platform assumptions describe this for S-CORE. .. toctree:: From 859b12e46a21a8530fa47913984d2c04b10cc471 Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Mon, 24 Nov 2025 09:14:43 +0000 Subject: [PATCH 15/15] fix review finding --- docs/score_releases/index.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/score_releases/index.rst b/docs/score_releases/index.rst index 80259e49ecc..035bba0399a 100644 --- a/docs/score_releases/index.rst +++ b/docs/score_releases/index.rst @@ -17,7 +17,9 @@ S-CORE Releases =============== -A **Release** is a crucial aspects of the project life cycle within the `Eclipse Development Process `_. It is a officially distributed, versioned, and deployable collection of Project artifacts intended for distribution beyond the Project Developers. It brings together the initial set of core modules, reference integrations, and supporting infrastructure needed to build. For further information about the platform releases and module releases see `release documentation `_ in the process description. +A **Release** is a officially distributed, versioned, and deployable collection of Project artifacts intended for distribution beyond the Project Developers. It brings together the initial set of core modules, reference integrations, and supporting infrastructure needed to build. For further information about the platform releases and module releases see `release documentation `_ in the process description. + +See also the project life cycle within the `Eclipse Development Process `_. S-CORE Releases Overview ========================