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 Deprecation]: urn:bamm:io.catenax.single_level_bom_as_planned:1.1.0 #372

Closed
3 tasks
bs-jokri opened this issue Oct 6, 2023 · 3 comments · Fixed by #424
Closed
3 tasks

[Model Deprecation]: urn:bamm:io.catenax.single_level_bom_as_planned:1.1.0 #372

bs-jokri opened this issue Oct 6, 2023 · 3 comments · Fixed by #424

Comments

@bs-jokri
Copy link
Contributor

bs-jokri commented Oct 6, 2023

Update Reason

The model is neither used in a standard document or triangle document, which indicates that the model is not used anymore.

If there are still reasons to still have this model in the repository, please provide a short rationale in the comments. If not, please indicate with a "+1" that you are OK with deprecating the model.

Deprecating a model means, that it will be removed after two Tractus-X releases from the repository. For details, please refer to the GOVERNANCE process.

MS1 Criteria

  • The model that should be deprecated exists and is not deprecated already
  • The respective model does not affect existing use cases (aspect is either used in higher versions or replaced by a different aspect)
  • A shared aspect, which will be deprecated, is not used by any released aspect model
@bs-jokri
Copy link
Contributor Author

bs-jokri commented Oct 6, 2023

@johannsvarela please check this request

@johannsvarela
Copy link
Contributor

johannsvarela commented Oct 6, 2023

@bs-jokri the model SingleLevelBomAsPlanned_1.1.0 can be set deprecated

@johannsvarela
Copy link
Contributor

FYI @jonbckr @BenediktMuellerIML

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants