R24.05 Digital Twin Registry (dDTR) - Release Checks

[agg3fe]

[!IMPORTANT]
Follow the guidance on how to use the templates.

Release Info

Please provide information on what you want to be included in the Eclipse Tractus-X release. If you are not owner of this issue, please provide the information as comment to the issue. Make sure to assign this issue to expert(s) for their approval, as soon as you have finished preparation. Multiple assignees allowed; they will un-assign themselves once review completed.

Version to be included in Eclipse Tractus-X release: helm: digital-twin-registry-0.4.11 Image version: 0.4.3

Leading product repository: https://github.com/eclipse-tractusx/sldt-digital-twin-registry

Compliance Verifications

This issue tracks all checks, that need to be performed for a product release in Eclipse Tractus-X.

• [x] Interoperability checks performed
• [x] Data Sovereignty checks performed

General Checks

• [x] Tractus-X Release Guidelines(TRGs) fulfilled

[!NOTE] Note: most criteria for documentation and security are now covered in TRGs

Security Checks

• [x] Thread Modelling Analysis passed

Test Results

• [x] E2E Integration Test passed
• [x] User Journey approved

Helpful Links

• Eclipse Tractus-X openAPI specs on SwaggerHub

[agg3fe]

Data Sovereignty Check: @vialkoje : Could you please tick this checkbox? No significant changes since Release 23.12 See also Description for R24.03

[agg3fe]

Interoperability Check: Interoperability was ensured to Release 23.12. Since then no changes have been made. HiHenrik : Could you please tick this checkbox?

[agg3fe]

Security Checks- Thread Modelling Analysis: No changes since Release 23.12. See also Security Assessment diagram: https://github.com/eclipse-tractusx/sldt-digital-twin-registry/tree/main/docs#security-assessment:~:text=Security-,Assessment,-Data%20flow%20diagram

@guenterban : Could you please check and approve it?

[agg3fe]

User Journey : @thomas-henn : Could you please confirm? See also previous task for R23.12: https://github.com/eclipse-tractusx/sig-release/issues/116

[agg3fe]

Security scanning: https://github.com/eclipse-tractusx/sldt-digital-twin-registry/security/code-scanning KICS: https://github.com/eclipse-tractusx/sldt-digital-twin-registry/actions/workflows/kics.yml Trivy: https://github.com/eclipse-tractusx/sldt-digital-twin-registry/actions/workflows/trivy.yml

[agg3fe]

@kelaja A self review of the TRGs have been done and everything looks good.

[thomas-henn]

Yes, I hereby confirm that the requirements for the "User Journey" of the Digital Twin Regsitry are fulfilled.

[guenterban]

Thread Modelling Analysis approved

[vialkoje]

as the digital twin registry follows the generic patterns for a data source and allows the correct configuration using the EDC the data sovereignty requirements are fulfilled and the expert approval is granted.

[agg3fe]

cbrugg: Could you please provide the approval for E2E integration tests passed.

[cbrugg]

E2E Tests as well as INT Tests have been performed successfully. Thank You!

[RolaH1t]

QG review 14-May Interoperability approval outstanding TRG crosscheck will be performed cw20; no blockers no follow-up mtg required

[RolaH1t]

Interoperability update: if your QG approval was not obtained by now via the communicated channels, please perform a self-assessment and document your results here. reference approval(s) of previous Release(s) - if applicable - and point out significant modifications relevant for InterOp - if any. (note: capacity of approving experts is very limited at this advanced point of time)

[RolaH1t]

@thomas-henn seems your self assessment on Interoperability is the only outstanding item before we can fully approve the QG. Thx, Roland

[RolaH1t]

??? where can the evidence for successful TRG checks be found ? add link please!

[agg3fe]

@thomas-henn seems your self assessment on Interoperability is the only outstanding item before we can fully approve the QG. Thx, Roland

Hi @RolaH1t Yes right. I just wanted to make sure that the interoperability also looks good. So Here by I confirm that we are aligned with interoperability and we do not have any changes in it since the past releases. Thanks, Sahil

[agg3fe]

??? where can the evidence for successful TRG checks be found ? add link please!

Hi @RolaH1t , Actually we did not create any ticket or separate checklist as evidence for TRG completion. We just had a look at every TRG together with Tuna and validated that every TRG is followed. Should we create a ticket separately, the way it was done previously?

[RolaH1t]

??? where can the evidence for successful TRG checks be found ? add link please!

Hi @RolaH1t , Actually we did not create any ticket or separate checklist as evidence for TRG completion. We just had a look at every TRG together with Tuna and validated that every TRG is followed. Should we create a ticket separately, the way it was done previously?

Hi @agg3fe this would be the "extra mile" but is not a hard pre-requisite. We take your confirmation with @tunacicek for granted.

[RolaH1t]

@thomas-henn seems your self assessment on Interoperability is the only outstanding item before we can fully approve the QG. Thx, Roland

Hi @RolaH1t Yes right. I just wanted to make sure that the interoperability also looks good. So Here by I confirm that we are aligned with interoperability and we do not have any changes in it since the past releases. Thanks, Sahil

perfect! pls check the relevant box so I can fully approve QG!

[agg3fe]

@thomas-henn seems your self assessment on Interoperability is the only outstanding item before we can fully approve the QG. Thx, Roland

Hi @RolaH1t Yes right. I just wanted to make sure that the interoperability also looks good. So Here by I confirm that we are aligned with interoperability and we do not have any changes in it since the past releases. Thanks, Sahil

perfect! pls check the relevant box so I can fully approve QG!

Thank you. Done.

[RolaH1t]

Congrats: Quality Gate fully approved with all necessary pre-requisites fulfilled! Thanks for all your efforts, Roland

[stephanbcbauer]

Hello @agg3fe

Since the feature is a 24.05 feature and the development phase for 24.08 is coming to an end, we need a status on the feature. Can you please update the status?

• [ ] Currently you are assigned (Responsible) → Is this correct? If not, please assign the correct contact person
• [x] Please check whether the status (backlog, work in progress ...) is set correctly
• [x] Please comment on the current status of the feature
• [x] Are all SubTasks (issues from other repositories that deal with the feature) linked? → The easiest way is to mention the feature here in the issue (via the ID) so we can see which teams/repositories are involved.
• [ ] Is there a spillover planned?

If you need any clarification, please get in touch, thank you very much.

Stephan

[agg3fe]

Hello @agg3fe

Since the feature is a 24.05 feature and the development phase for 24.08 is coming to an end, we need a status on the feature. Can you please update the status?

• [ ] Currently you are assigned (Responsible) → Is this correct? If not, please assign the correct contact person
• [ ] Please check whether the status (backlog, work in progress ...) is set correctly
• [ ] Please comment on the current status of the feature
• [ ] Are all SubTasks (issues from other repositories that deal with the feature) linked? → The easiest way is to mention the feature here in the issue (via the ID) so we can see which teams/repositories are involved.
• [ ] Is there a spillover planned?

If you need any clarification, please get in touch, thank you very much.

Stephan

Hi @stephanbcbauer Our features from 24.05 release are completed and all related activities are done including the updates in "Release 24.05 View" inside "Release Planning" board. Please let me know if you expect anything more from our team.

[agg3fe]

As the task is complete and approval is granted, closing the issue. please reopen or let us know incase something.