search

eclipse-tractusx / sig-release

https://eclipse-tractusx.github.io/sig-release
Apache License 2.0
8 stars 10 forks source link

R24.03 PURIS Release Checks #510

Closed kelaja closed 7 months ago

kelaja commented 9 months ago

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.

Version to be included in Eclipse Tractus-X release: 1.0.0

Leading product repository: eclipse-tractusx/puris

Compliance Verifications

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

Documentation

Security Checks

General Checks

Test Results

Helpful Links

tom-rm-meyer-ISST commented 9 months ago

@kelaja I already inserted the version and repository in your initial statement. Release still needs to be created, but version number will be 1.0.0 for R24.03

szymonkowalczykzf commented 8 months ago

Security Assessment Process (Threat Modeling Analysis) approved.

Re-assessment was done on Friday 16th Feb 2024. No open critical & high findings remains. Documentation of the assessment will be uploaded to the PURIS docs repo soon.

DirkBTSI commented 8 months ago

INT test performed/documented. E2E test performed/documented. No high defect. TM approved @kelaja  : please approve for "E2E Integration Test passed"

tom-rm-meyer-ISST commented 8 months ago

@vialkoje Please approve the documentation. The changes requested in your mail, habe been incorporated.

This link will guide you to the documents.

Please also approve data sovereignty. We have a concept, and configuration instructions / hints.

tom-rm-meyer-ISST commented 8 months ago

@wjost, could you please check the GAIA-X compliance, as this is our first assessment?

tom-rm-meyer-ISST commented 8 months ago

@HiHenrik, could you please approve the interoperability? We had a session with Thomas on 2024-01-29 during office hour that can be found in confluence.

tom-rm-meyer-ISST commented 8 months ago

@RoKrish14 could we align on the remaining security items?

tom-rm-meyer-ISST commented 8 months ago

@jjeroch Could you please check the styleguide open points. You'll find all details in my email from 2024-02-16.

RolaH1t commented 8 months ago

QG review executed as per plan. Tom actively consolidating the outstanding items. Approval postponed until topics are addressed. Cross-check scheduled for 28-Feb

tom-rm-meyer-ISST commented 8 months ago

Catena-X GDPR Declaration and Requirements_V3_filled.xlsx @RolaH1t, @kelaja, please find attached my Excel for GDPR. Only points would be IP (commonly company or ISP IP) and a uuid that is logged for user authentication. I guess it's not GDPR relevant, isn't it?

HiHenrik commented 8 months ago

@HiHenrik, could you please approve the interoperability? We had a session with Thomas on 2024-01-29 during office hour that can be found in confluence.

Approved for interoperability as discussed in interop office hour

rauschg commented 8 months ago

Customer journey is approved by me as BO after review with @tom-rm-meyer-ISST was done this week.

RoKrish14 commented 8 months ago

Was a plesaure @tom-rm-meyer-ISST

SAST: Approved SCA: Approved DAST: Approved Secret scans: Approved Container scans: Approved IAC: Approved

jjeroch commented 8 months ago

@tom-rm-meyer-ISST as discussed - the gateway criteria "Compliant with the Style Guide" is for this release descoped/not under review due to the time criticality which we are currently facing. It is known that the PURIS solution does not yet follow the CX-UI-style-guide and need to get urgently updated as part of 24.05. release.

Please highlight this information in the release approval as well as under your ChangeLog of the FE component under "Known Knowns" Let me know in case you need anything else.

Just a couple of statements as preparation of 24.05.:

tom-rm-meyer-ISST commented 8 months ago

@tom-rm-meyer-ISST as discussed - the gateway criteria "Compliant with the Style Guide" is for this release descoped/not under review due to the time criticality which we are currently facing. It is known that the PURIS solution does not yet follow the CX-UI-style-guide and need to get urgently updated as part of 24.05. release.

Please highlight this information in the release approval as well as under your ChangeLog of the FE component under "Known Knowns" Let me know in case you need anything else.

Just a couple of statements as preparation of 24.05.:

  • please check the "view edc catalog" implementation - I wonder if this would make much more sense if you connect to the dataspace discovery service to find edc urls based on provider/customer business partner numbers
  • /transfers running on a 500 service error 🚩
  • /negotiations page is empty - unclear for the user whats happening here - I suggest a "currently no negotiations existing" screen. Likely things like filters, search, etc will be useful
  • application help missing
  • grey/white input field usage incorrect implemented. Grey-out if no input is expected
  • missing uder feedback if I "add" or "update" anything in the stock
  • same as above applies for "Update partner stock"
  • already pre-info for 24.05.: configuration for auto-negotiation required or a management board to run negotiations

Already incorporated in Changelog and Release.

tom-rm-meyer-ISST commented 8 months ago

@wjost, could you please check the GAIA-X compliance, as this is our first assessment?

Friendly reminder: @wjost, could you please check the GAIA-X compliance, as this is our first assessment?

vialkoje commented 8 months ago

Documentation existing and well structured. Content is looking consistent. regarding Itnerface documentation - please consider providing also an OpenAPI documentation e.g. in Swagger HUB !

Expert Approval Granted for Documentation.

No changed requirements for data sovereignty - Expert Approval granted. Please consider Sovereignty QG-Requirements for release 24.05 !

tomaszbarwicki commented 8 months ago

QG checks completed: https://github.com/eclipse-tractusx/puris/issues/257

wjost commented 8 months ago

For GX-Compliance the ServiceOffering SD for the related EDC instances had to be provided from the associated participants/operators of the Puris node and the LegalPerson SD of the operator/participant. These SD will be provided by the Portal hence nothing more to be done for PURIS. Expert Approval granted for GX Compliance

RolaH1t commented 8 months ago

all pre-conditions now fulfilled QG approval granted Congrats!!!