What
Some of our feature requirements are not planned for v1 and so the PR eclipse-score/score#3249 set those to invalid:
feat_req__lifecycle__running_processes
feat_req__lifecycle__oci_compliant
feat_req__lifecycle__query_commands
feat_req__lifecycle__controlif_status
feat_req__lifecycle__recov_run_target_switch
feat_req__lifecycle__smart_watchdog_config
feat_req__lifecycle__multi_instance_support
feat_req__lifecycle__config_file_support
feat_req__lifecycle__session_extension
feat_req__lifecycle__deps_visualization
Should these be set to valid and use the valid_from field.
Seems that since docs-as-code 8.2.0 the tracking of feature reqs works with the valid_from should work https://github.com/eclipse-score/docs-as-code/releases/tag/v8.2.0
Acceptance Criteria (DoD)
How
No response
What
Some of our feature requirements are not planned for v1 and so the PR eclipse-score/score#3249 set those to
invalid:Should these be set to
validand use thevalid_fromfield.Seems that since docs-as-code 8.2.0 the tracking of feature reqs works with the valid_from should work https://github.com/eclipse-score/docs-as-code/releases/tag/v8.2.0
Acceptance Criteria (DoD)
How
No response