[R24.12] [Portal] Release Checks

[evegufy]

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.

Responsible contacts:

• Committer: @evegufy @Phil91 @ntruchsess @oyo
• Contributor contact: @MaximilianHauer

Version to be included in Eclipse Tractus-X release: 2.3.0 [NOT YET RELEASED]

Portal:

• Portal Chart: portal-2.3.0
• Portal Frontend: v2.3.0
• Portal Backend: v2.3.0
• Portal Assets: v2.3.0
• Portal Frontend Registration: v2.1.0

IAM:

• CentralIdP: 4.0.0
• SharedIdP: 4.0.0

Leading product repository: Portal

Compliance

• Possible changes (through the new features) on related Catena-X standards are considered and addressed
• Tractus-X Release Guidelines(TRGs) fulfilled

Make sure to open and fill in a separate documentation issue in your product repository using the Quality Gate Checklist issue template

Note

Note: most criteria for documentation and security are now covered in TRGs

Functionality

• Feature works as expected and described
• Backward compatibility maintained (depending Major/ Minor)

Performance

• Memory and CPU usage is within acceptable limits oriented with goldilocks

Testing

• Unit tests cover all new features
• Integration tests are updated
• E2E/Integration test passed
• Regressions tests passed

Feature summary

Please provide a list of all features that have been developed in the current phase. This list is essential for several reasons:

• Test Preparation: Identifying new features will help in the creation of new end-to-end (E2E) tests and ensure that the relevant aspects are thoroughly tested.
• Awareness: It will raise awareness of the features that need to be prioritized during the testing process.
• Board Management: This will assist in keeping the project board organized and up-to-date.

By documenting these features, you will contribute to a smoother and more efficient release process.

Note

Note: all features needs to be closed to get approval for release

Feature	Test Status	Note
Upload business partner data as .CSV #700	Test status
Enhancement of Technical User E2E Experience in Dataspace #789	Test status
Clearinghouse Connection Management and SD Document Job Handling #796	Test status
Asynchron Technical User Management - Enhancement of Technical User Deletion #803	Test status
Onboarding Service Provider Dashboard/Management Board #809	Test status
Process Workers: Validation and Development of Missing Process Worker Retriggers #811	Test status
Improve initial wallet insert and credential creation #781	Test status
Enhancement Keycloak seeding job to seed variables and secrets #578	Test status
IAM and BPDM: Adjust to Rights and Role Concept #751	Test status
Upgrade to Keycloak version 25	Test status
R24.12 Technical Maintenance #779	Test status
Publish API specifications to API Hub #804	Test status
Align documentation structure with updated TRG 1 #805	Test status

For a more detailed insight, please see the milestones:

Repository	Milestones
Portal	2.2.0, 2.3.0
Portal Frontend	2.2.0, 2.3.0
Portal Backend	2.2.0, 2.3.0
Portal Assets	2.2.0, 2.3.0
Portal Frontend Registration	2.1.0
Portal IAM	4.0.0

Release Documentation

• Release notes/Changelogs are updated
• Migration scripts/documentation are included if necessary (Ensure that any database or infrastructure migrations are included).
• Known knowns
  • topic 1
  • topic 2

Summary

Please provide a short summary about the new values/benefits of the new features here:

• description of the value of feature 1
• description of the value of feature 2

Helpful Links

• Eclipse Tractus-X openAPI specs on SwaggerHub

[ybidois]

Hi @evegufy, sorry, we were super busy with the Go Live. We'll look into what is done in the next days. How long do we have to finish our features?

[evegufy]

Hi @evegufy, sorry, we were super busy with the Go Live. We'll look into what is done in the next days. How long do we have to finish our features?

as discussed, it's too late for 24.12 and you move #812 and #815 to 25.03