Skip to content

Conversation

yselkowitz
Copy link
Collaborator

/cc @omajid

@omajid
Copy link
Contributor

omajid commented Oct 21, 2024

Please note that the EOL of dotnet8.0 is later. Should we add dotnet9.0? This package is basically the same scenario as dotnet7.0 which was put in unwanted instead: #1040

@yselkowitz
Copy link
Collaborator Author

7.0 was marked unwanted when 8.0 was already around to supersede it. As it looks like 9.0 is going to be in c10s, we want to track it (at least there) and not mark it unwanted yet. Once 10.0 is out (late next year?) then we'll want to mark 8.0 and 9.0 unwanted in ELN, and drop them from c10s once they go out of support.

Another advantage of tracking 9.0 in ELN is the potential to find issues leading up to 10.0 which we wouldn't necessarily get by only tracking 8.0.

@omajid
Copy link
Contributor

omajid commented Oct 21, 2024

Okay, that works for me!

@yselkowitz yselkowitz merged commit 63ba0af into minimization:main Oct 21, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants