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.

Sign up for GitHub

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

Jump to bottom

Fully support metamodel versioning #556

Open
sstone1 opened this issue Dec 2, 2022 · 6 comments · May be fixed by #986
Open

Fully support metamodel versioning #556

sstone1 opened this issue Dec 2, 2022 · 6 comments · May be fixed by #986
Labels
Difficulty: Challenging Type: Need Investigation 🔬

Comments

@sstone1
Copy link
Contributor

sstone1 commented Dec 2, 2022

Metamodel versioning has been introduced, but the entire codebase is hardcoded to [email protected], and so we can only support metamodels using this specific version. This limits us when making metamodel changes, as it is not currently possible to deliver a new metamodel version into Concerto and have Concerto still process existing metamodels that use the old version.

This feature should extend Concerto such that we can support existing 1.0.0 version metamodels and a new 1.1.0 version metamodel at the same time, as well as defining the strategy for how we eventually support a new 2.0.0 version. Will we support both 1.x and 2.x metamodels at the same time, or will we introduce a new major version of Concerto?
@mttrbrts mttrbrts mentioned this issue Dec 2, 2022
Merged
5 tasks
@sstone1 sstone1 mentioned this issue Dec 7, 2022
Closed
@mttrbrts mttrbrts moved this to Next 3 Months in Concerto Roadmap Dec 9, 2022
@mttrbrts mttrbrts moved this from Next 3 Months to Next 6 Months in Concerto Roadmap Dec 9, 2022
@mttrbrts mttrbrts moved this from Next 6 Months to Next 3 Months in Concerto Roadmap Dec 9, 2022
@mttrbrts mttrbrts moved this from Next 3 Months to Next 6 Months in Concerto Roadmap Nov 8, 2023
@github-actions GitHub Actions
Copy link
Contributor

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 10 days.

@github-actions github-actions bot added the Stale label Dec 10, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 22, 2024
@github-project-automation github-project-automation bot moved this from Next 6 Months to Done in Concerto Roadmap Dec 22, 2024
@DianaLease DianaLease removed the Stale label Jan 22, 2025
@DianaLease DianaLease reopened this Jan 22, 2025
@Atul-khadse
Copy link

Hi @DianaLease, I would like to work on this issue. Could you please provide more details or guidance on how to get started? I’ll begin by investigating how to extend Concerto for supporting multiple metamodel versions

@Atul-khadse
Copy link

I think update the ModelManager to handle multiple metamodel versions.

@Atul-khadse Atul-khadse linked a pull request Feb 4, 2025 that will close this issue
Open
@sanketshevkar
Copy link
Member

Thanks a lot for the PR. But we first need to decide on the strategy how do we support multiple versions of metamodel first and then make relavant changes.

Happy to hear you opinions on the issue discssion board. Thanks!

@Atul-khadse
Copy link

Thank you for the feedback! That makes sense. I'll join the discussion on the issue board to share my thoughts on the strategy for supporting multiple metamodel versions. Looking forward to collaborating on defining a clear approach before making the relevant changes.

@DianaLease DianaLease moved this from Done to Next 12 Months in Concerto Roadmap Feb 12, 2025
@DianaLease
Copy link
Member

Ideas from Tech WG call on Feb 12:

  • Extend the metamodel package to expose all versions of the metamodel and add a method (getMetaModelVersion) to the model manager to dynamically retrieve the metamodel version
  • Do the same for decorator set model
  • Related to Semver imports #931, support semver versioning so that rather than hardcoding 1.0.0 we can use something like 1.x

Recording from call for reference: https://vimeo.com/1055995177?share=copy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Difficulty: Challenging Type: Need Investigation 🔬
Projects
Concerto Roadmap
Status: Next 12 Months
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update the ModelManager to handle multiple metamodel versions. Atul-khadse/concerto
5 participants
@sstone1 @mttrbrts @DianaLease @sanketshevkar @Atul-khadse