Repository navigation
Conversation
github-project-automation
Bot
added this to
TLC - Technical Lead Circle and S-CORE Roadmap
Contributor
|
Documentation preview for this pull request is available at: |
TimoSteuerwaldETAS
force-pushed
the
feature/requirements_clarification
branch
from
September 30, 2026 14:04
e908ca4 to
2f95ec9
Compare
MaciejKaszynski
requested changes
Sep 30, 2026
MaciejKaszynski
left a comment
MaciejKaszynski
left a comment
Contributor
There was a problem hiding this comment.
Small wording nit picks
TimoSteuerwaldETAS
marked this pull request as ready for review
October 1, 2026 12:46
TimoSteuerwaldETAS
requested review from
a team,
4og,
FScholPer,
LittleHuba,
anmittag,
antonkri,
arsibo,
johannes-esr,
michaelsaborov,
pawelrutkaq,
qor-lb,
ramceb,
rmaddikery and
umaucher
as code owners
October 1, 2026 12:46
See comp_req__launch_man__dep_based_startup_order
See comp_req__launch_man__launch_parallel
As this requirement is needed to serve as a basis on component level for all kind of dependencies between components.
These 3 requirements have been moved to component level or were already existent there: feat_req__lifecycle__start_named_run_target -> comp_req__launch_man__start_named_run_target feat_req__lifecycle__switch_run_targets -> comp_req__launch_man__switch_run_targets feat_req__lifecycle__recov_run_target_switch -> comp_req__launch_man__recovery_switch_rt
Co-authored-by: Maciej Kaszynski <161459353+MaciejKaszynski@users.noreply.github.com> Signed-off-by: Timo Steuerwald <142218678+TimoSteuerwaldETAS@users.noreply.github.com>
See also meeting minutes from 15. July.: feat_req__lifecycle__custom_cond_support can be deleted as long as there is another requirement which asks for a Control Interface to switch Run Targets. For this use case we already have feat_req__lifecycle__control_commands Introduced feat_req__lifecycle__sandbox_options instead, because deleted feat_req__lifecycle__custom_cond_support had many derived component requirements, which are about the sandbox options (like UID, GUID, process priority, scheduling, etc.) and unrelated to the original feature requirement. Some rephrasing as requested by code review.
TimoSteuerwaldETAS
force-pushed
the
feature/requirements_clarification
branch
from
October 1, 2026 12:47
1d6c311 to
b6783a8
Compare
Member
|
@TimoSteuerwaldETAS please have a look into the findings |
MaciejKaszynski
approved these changes
Oct 6, 2026
Contributor
|
@aschemmel-tech and @ramceb could you take a look? |
FScholPer
approved these changes
Oct 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See eclipse-score/lifecycle#730 for description