EDC - Maintenance

[lgblaumeiser]

Description

As a member of the EDC developer community,

I want to have a clean code base that follows the latest development guidelines

Therefore come code hygiene measures should be taken up, to clean up the code base, like:

• Extension hygiene: Getting rid of unsupported/not officially sanctioned extensions
• Extension refactoring: Rewrite/redesign legacy extensions that aren't up to Tx-EDC standards and coding guide lines
• Settings hygiene: All Tractus-X EDC properties should start with tx.edc. to be able to clearly distinguish them. We should go through all extensions and fix that. --> Harmonize Tractus-X EDC Settings tractusx-edc#1302

Initial creator: @paullatzelsperger

@paullatzelsperger: Feel free to extend the current description, we thought, that from a planning point of view, we could summarize these three points to one planning item and create concrete workitems during the development iteration.

Impact

None expected

Additional information

• I'm willing to contribute to this feature

[paullatzelsperger]

@lgblaumeiser that's fine for the time being. Ultimately all three of these items should become issues in the tractusx-edc repo

[stephanbcbauer]

was presented in the open planning ⇾ contributors and committer are involved.

[stephanbcbauer]

Hello @paullatzelsperger, @lgblaumeiser

Since the feature is a 24.08 feature and the development phase is coming to an end, we need a status on the feature.

• 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 check whether there is an assignment to a committee or expert group (supported-by) to be found on the board
• 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.

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

[paullatzelsperger]

@stephanbcbauer this is a long-running issue, that is never really "done". I cannot tell you all maintenance tasks that'll ever be in advance, because we typically refactor, cleanup and maintain when we come across problems.

TL;DR: we could close this issue, and create dedicated ones whenever we do a refactoring, WDYT?

[lgblaumeiser]

2024-06-11: Onoging activity, will be closed close to release with a documentation of issues closed during the development cycle.

[lgblaumeiser]

2024-06-11:

• 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 check whether there is an assignment to a committee or expert group (supported-by) to be found on the board
• Please comment on the current status of the feature:
  Ongoing activity, will be closed close to release with a documentation of issues closed during the development cycle.
• 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.
  @paullatzelsperger : Please add all activity issues and PRs connected to this activity to the item.

[lgblaumeiser]

Will be closed with the release of the Tractus-X connector

[stephanbcbauer]

Hello @lgblaumeiser

In a few weeks, we want to publish Tractus-X Release 24.08. For this, we need a clear status about the features (which will be included in the release and which will be cancelled or postponed to the next release).

Currently, the feature is still in status Work in progress. Please update the status by 09.07.24 eob.

If the feature is not ready for release 24.08, or it is possibly not planned at all, please set the status to Not in release. Please remember that in this case, any dependent components must be informed.

Thank you and best regards.

[lgblaumeiser]

Hi @paullatzelsperger @wolf4ood @ndr-brt

can you add links to PR which you would rate under this category, so that we can close the issue, thanks!

[paullatzelsperger]

answering for myself, listing a few Tx-EDC ones:

• fix: adopt EDC test runtime model tractusx-edc#1355
• feat(ci): add multi-k8s versions test tractusx-edc#1314
• chore: harmonize settings names (with backwards compat) tractusx-edc#1307
• chore: remove SFTP extension modules tractusx-edc#1223

[wolf4ood]

adding few more:

• chore: bumps to EDC 0.8.0 tractusx-edc#1414

[ndr-brt]

• docs(api): fix published api specs tractusx-edc#1399
• docs(api): get openapi files from dependencies repository tractusx-edc#1402
• build(deps): align eclipse-temurin versions to 22.0.1_8-jre-alpine tractusx-edc#1309
• refactor: remove deprecated signaling api context configuration tractusx-edc#1340