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

[FEAT] Create strategy for supporting different platform versions #3137

Open
griest024 opened this issue Oct 3, 2024 · 1 comment
Open
Assignees
Labels
feat a new feature, enhancement, or improvement layer: driver This PR or issue is related to the driver layer of Daffodil

Comments

@griest024
Copy link
Member

💡 Feature request

Feature Name

Create strategy for supporting different platform versions

The Desired Behavior

The following questions need answers:

  • When a new version of a platform is released and we update the driver, what happens to the previous version?
  • What should the migration path be for apps that upgrade to the new platform version?
  • What should the migration path be for apps that don't upgrade to the new platform version but upgrade to a new daffodil version?
@griest024 griest024 added feat a new feature, enhancement, or improvement layer: driver This PR or issue is related to the driver layer of Daffodil labels Oct 3, 2024
@griest024
Copy link
Member Author

An interesting solution is having a separate installable library that tracks platform versions instead of daffodil versions. Daffodil could introduce breaking changes but only by changing the driver interface. This would allow apps to upgrade platform drivers and daffodil separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat a new feature, enhancement, or improvement layer: driver This PR or issue is related to the driver layer of Daffodil
Projects
None yet
Development

No branches or pull requests

2 participants