Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Model Update]: PCF #300

Closed
6 of 7 tasks
SMaierTSI opened this issue Sep 11, 2023 · 3 comments · Fixed by #306
Closed
6 of 7 tasks

[Model Update]: PCF #300

SMaierTSI opened this issue Sep 11, 2023 · 3 comments · Fixed by #306
Labels
MS1_Approved Checklist "MS1 Request for Model Developement" is approved.

Comments

@SMaierTSI
Copy link
Contributor

SMaierTSI commented Sep 11, 2023

Update Reason

After release of the latest PCF data model v4.0.1 there were some change requests which need to be implemented in an updated version (e.g. missing properties, adaptation of mandatory/ optional declarations, etc.). All findings are documented in CX confluence.

MS1 Criteria

  • The model that should be updated exists
  • The referenced use case exists
  • The potential updates are discussed with all stakeholders
  • A decision on versioning was made in consensus with the affected parties according to the guidelines.
  • The potential update will be either
    • backward compatible or
    • a (chain of) migration strategy(-ies) from all non-deprecated previous versions to the new model will be developed
@SMaierTSI
Copy link
Contributor Author

@Modeling_Team

@bs-jokri
Copy link
Contributor

The version will be 5.0.0 as it is not backwards compatible

@bs-jokri bs-jokri added the MS1_Approved Checklist "MS1 Request for Model Developement" is approved. label Sep 11, 2023
@bs-jokri
Copy link
Contributor

@agg3fe will be modeling steward for the model

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MS1_Approved Checklist "MS1 Request for Model Developement" is approved.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants