Skip to content

Stop producing Crossgen2 transport package (use Crossgen2 pack downstream instead) #1869

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.

Sign up for GitHub

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

Jump to bottom
Closed
dagood opened this issue Jan 17, 2020 · 3 comments
Closed

Stop producing Crossgen2 transport package (use Crossgen2 pack downstream instead) #1869

dagood opened this issue Jan 17, 2020 · 3 comments
Labels
area-crossgen2-coreclr
Milestone
6.0.0

Comments

@dagood
Copy link
Member

dagood commented Jan 17, 2020

The Crossgen2 pack (#906) will be built using live bits in the dotnet/runtime official build, so the transport pack is no longer necessary for that flow.

I'm not deleting the transport package infra right away because there may be some external dependencies on it. We should determine if there are any, and delete the redundant nupkg.

@fadimounir
@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added area-CrossGen/NGEN-coreclr untriaged New issue has not been triaged by the area owner labels Jan 17, 2020
@dagood dagood mentioned this issue Jan 17, 2020
Merged
@jeffschwMSFT jeffschwMSFT added this to the 5.0 milestone Jan 22, 2020
@jeffschwMSFT jeffschwMSFT removed the untriaged New issue has not been triaged by the area owner label Jan 22, 2020
@dagood dagood mentioned this issue Jan 30, 2020
Closed
@mangod9 mangod9 modified the milestones: 5.0.0, 6.0.0 Aug 10, 2020
@mangod9
Copy link
Member

mangod9 commented Aug 10, 2020

@AntonLapounov is there any work required here?

@AntonLapounov
Copy link
Member

@dagood It seems we stopped producing transport.Microsoft.NETCore.Crossgen2 package in February 2020. Can this be closed now?
https://dev.azure.com/dnceng/public/_packaging?_a=package&feed=dotnet5&view=versions&package=transport.Microsoft.NETCore.Crossgen2&version=5.0.0-alpha.1.20104.1&protocolType=NuGet

@dagood
Copy link
Member Author

dagood commented Sep 16, 2020

Yep. Seems fine to assume that either someone checked for dependencies before doing the removal, or if there were some unknown dependency, someone would have filed an issue about it since then.

@dagood dagood closed this as completed Sep 16, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-crossgen2-coreclr
Projects
None yet
Milestone
6.0.0
Development

No branches or pull requests
6 participants
@jkotas @jeffschwMSFT @dagood @AntonLapounov @Dotnet-GitSync-Bot @mangod9