-
Notifications
You must be signed in to change notification settings - Fork 136
Support multiple feature bands #2694
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
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Every feature band involves some work. I guess one of the driving reasons for feature bands is to ensure compatibility for visual studio. cc @omajid |
Agreed. I think we care more about backwards compat for source-build users. We would be okay with new features, but it's backwards compat that have a large impact. Red Hat ships any feature band upgrades as monthly updates. That means customers will upgrade to new feature bands (without any choice) to get CVE fixes. Any backward incompatibility in the feature band has a risk of breaking users building .NET applications, and is almost too risky for the users/customers Red Hat cares about. |
Scenario:
The text was updated successfully, but these errors were encountered: