Closed ciprianherciu closed 3 months ago
Please note that there was the following update to the issue template (see https://github.com/eclipse-tractusx/sig-release/pull/750#issuecomment-2219591340 for additional information), please take that into account for R24.08
Make sure to open and fill in a separate documentation issue in your product repository using the Quality Gate Checklist issue template
Hi, as discussed in today's open meeting and referring to today's email, please remove the check topics for Interoperability, Data Sovereignty and Threat Modeling in your description.
QG-Review 23-July
Planned E2E Tests for release 24.08 on Catena-X INT environment have been performed successfully. Thank You!
@ciprianherciu Could you set the check for the e2e test and could you give me an update on how far you are with the TRGs?
@almadigabor could you give me an update on how far you are with the TRGs? :)
I approve the QG with the following version numbers:
Helm Chart Version: 1.6.0 App Version: 1.5.7
I have a question. The TRG 9.01 UI consistency/styleguide for UI is not checked. Is this on purpose, because no committer has checked it or was the check forgotten?
@ther3sa MSO does not have a UI
@ther3sa MSO does not have a UI
okay thank you :)
@ciprianherciu Can you update the version in the description to the newest. Then I will give my approval. :)
Congrats: Quality Gate fully approved with all necessary pre-requisites fulfilled! Thanks for all your efforts :)
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: version placeholder Helmchart version 1.6.0 AppVersion - 1.5.7 Leading product repository: repository link
General Checks
Make sure to open and fill in a separate documentation issue in your product repository using the Quality Gate Checklist issue template
Test Results
Helpful Links