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

CLI Compatibility Strategy #110

Closed
6 tasks done
iliapolo opened this issue Feb 3, 2020 · 0 comments · Fixed by #111
Closed
6 tasks done

CLI Compatibility Strategy #110

iliapolo opened this issue Feb 3, 2020 · 0 comments · Fixed by #111
Assignees
Labels
effort/medium Reasonable effort required for implementation management/tracking status/done Implementation complete

Comments

@iliapolo
Copy link
Contributor

iliapolo commented Feb 3, 2020

PR Champion
#111 @eladb

Description

Devise a strategy for assuring we keep our CLI vs Framework Compatibility promises to customers:

  • New CLI versions should always support older framework versions.

  • New Framework versions might require a CLI upgrade.

    In which case, we display an error message instructing the user which version to upgrade to.

Progress

  • Tracking Issue Created
  • RFC PR Created
  • Core Team Member Assigned
  • Initial Approval / Final Comment Period
  • Ready For Implementation
  • Resolved
@iliapolo iliapolo self-assigned this Feb 3, 2020
@iliapolo iliapolo added the effort/medium Reasonable effort required for implementation label Mar 11, 2020
@iliapolo iliapolo added status/approved Ready for implementation and removed status/proposed Newly proposed RFC labels Apr 12, 2020
@eladb eladb changed the title Compatibility Assurance Strategy CLI Compatibility Strategy Apr 14, 2020
@eladb eladb added status/done Implementation complete and removed status/approved Ready for implementation labels Jun 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/medium Reasonable effort required for implementation management/tracking status/done Implementation complete
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants