Skip to content

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

Open
MichaelSimons opened this issue Dec 17, 2021 · 3 comments
Open

Support multiple feature bands #2694

MichaelSimons opened this issue Dec 17, 2021 · 3 comments
Assignees
Labels
area-unified-build Epic Groups multiple user stories. Can be grouped under a theme.

Comments

@MichaelSimons
Copy link
Member

Scenario:

  • Multiple feature bands (e.g. 6.0.1xx and 6.0.2xx) are released on the same day.
  • Source-build today only supports building each release tarball separately which each produce a copy of the runtime (logically identical).
  • Source-build tooling should support building and releasing both but with a shared runtime just like the Microsoft release.
@ghost ghost added the untriaged label Dec 17, 2021
@ghost
Copy link

ghost commented Dec 17, 2021

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.

@MichaelSimons MichaelSimons added area-infra Source-build infrastructure and reporting and removed untriaged labels Jan 6, 2022
@tmds
Copy link
Member

tmds commented Jun 14, 2022

Every feature band involves some work.
If there is enough compatibility, having the latest would be preferable.

I guess one of the driving reasons for feature bands is to ensure compatibility for visual studio.
I think this is less important for source-built .NET.

cc @omajid

@omajid
Copy link
Member

omajid commented Jun 14, 2022

I guess one of the driving reasons for feature bands is to ensure compatibility for visual studio. I think this is less important for source-built .NET.

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.

@MichaelSimons MichaelSimons added the Epic Groups multiple user stories. Can be grouped under a theme. label Mar 25, 2025
@MichaelSimons MichaelSimons changed the title Source-build should support multiple feature bands releasing concurrently Support multiple feature bands Mar 25, 2025
@MichaelSimons MichaelSimons added area-unified-build and removed area-infra Source-build infrastructure and reporting labels Mar 25, 2025
@mthalman mthalman moved this to In Progress in .NET Unified Build May 20, 2025
@mthalman mthalman self-assigned this May 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-unified-build Epic Groups multiple user stories. Can be grouped under a theme.
Projects
Status: In Progress
Development

No branches or pull requests

4 participants