Provide private feed with official nightly build

We should provide official nightly build to allow users to consume fix/features ASAP and avoid to release official nuget packages, this help for some reason to me:

• New features fix could be “tested” in real project, for instance corefx codebase could pickup nuget package from private feed and do feedback very quick, corefx is used every day by a lot of dev(@ViktorHofer).

• https://github.com/tonerdo/coverlet/pull/402 We are about to become The cross platform solution for Code Coverage generation for .NET Core projects(in a consistent manner). likely a lot of user will use coverlet from non win system. DataCollector will be picked up as nuget package, with private feed they can simply update PackageReference add private feed and consume fix/features in a fast way(@vagisha-nidhi).

We could start using:

• myget service for open source https://www.myget.org/opensource
• New github package registry https://github.com/features/package-registry

BTW I don’t know if foundation could help with better choice cc: @onovotny Maybe azure blob storage?

@tonerdo I propose also to move CI to Azure Pipelines, I found command trigger very useful to re-run pipeline https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/github?view=azure-devops&tabs=yaml#comment-triggers at the moment I cannot re-run appveyor CI from PR, I don’t know if it’s supported.

/cc @tonerdo @petli

[MarcoRossignoli]

In the meantime, how do you feel about moving your versioning to a major.minor.height pattern?

I’m fixing “nightly release” with new versioning, I think could work for coverlet we could move only major.minor by hand and use automatic height for PATCH, I like it. After that I’ll move nightly release to release pipeline and will remove ps script to have a clean and simple workflow. When nightly release will be ok(stable) and we feel ok with “new model”(we moved to AZP few time ago, I use AZP in my day by day job since 1.5 year as a full CICD for some asp.net core web sites but I never tackle lib versioning problem with that, so your guidelines are very appreciated and I’m taking advantage of it 😄 ) I think we could release all throught AZP.

[AArnott]

How we can know which heighted release refer to which master commit for troubleshooting?

1. Call nbgv get-commits <version> where <version> is the 3 or 4 integer version from the package or the assembly file version. See nbgv.
2. Work backwards through the releases in Azure Pipelines to find the version number that matches and look up the commit that the build was based on.