search

dotnet / buildtools

Build tools that are necessary for building the .NET Core projects
477 stars 240 forks source link

Can we disable master ? #2269

Closed danmoseley closed 3 years ago

danmoseley commented 4 years ago

@safern @ViktorHofer do the servicing branches of the old repos consume the v3.0 branch? If so would it make sense to tag and delete master in this repo as we did in those? That would help make clear that this repo is dead.

safern commented 4 years ago

Machine learning repo is still using buildtools, however I don't know how many fixes they often need... I think the plan for them is already to move to arcade soon, so it might just make sense to delete the master branch.

cc: @eerhardt @frank-dong-ms

frank-dong-ms-zz commented 4 years ago

Can somebody please help us understand the impact of disable master? We have a discussion on arcade but seems we don't have bandwidth to move to arcade in near future due to the cost.

cc: @harishsk

ViktorHofer commented 4 years ago

I would not delete master before all repos moved off it. My recommendation for dotnet/machinelearning would be to invest in moving to arcade. Maybe @markwilkie's team can help with that?

danmoseley commented 4 years ago

Ah, I didn't realize ML was still on it. Well, if it works..

terrajobst commented 4 years ago

Is ML the only repo still using buildtools?

safern commented 4 years ago

I think so. I don't know of any other repo using buildtools.

eerhardt commented 4 years ago

It's the only one I know of as well.

@harishsk - are there any plans of moving dotnet/machinelearning to arcade?

harishsk commented 4 years ago

Yes, we have discussed moving to Arcade internally several times. We had deferred it earlier because we had other blocking test issues and it wasn't clear whether moving to Arcade would improve that. We are now close to resolving our other test issues and we can bring this back on the table.

Is there a particular timeline you are looking at for the transition?

ViktorHofer commented 3 years ago

// Auto-generated message

Going forward, the .NET team is using https://github.com/dotnet/arcade to develop the code and issues formerly in this repository. Feel free to reopen/move this issue if it still applies to servicing branches in this repository, or source code which now resides in the Arcade repository.