My team are looking to push our shared code to a private NuGet feed in Azure Artifacts. At present the plan is to set the package version in our csproj files and set up CI on the master branch of each library's repo.
For production this flow is fine, but we'd also like to be able to iterate on new library versions and share those iterations with other developers on the same project before the new version of the library is finalized.
One way of doing this would be to use a second, pre-production NuGet feed and set up CI from a development branch to that feed. But I was wondering if we could keep things to a single feed by using Azure Artifacts views functionality.
So the general idea is - be able to package and share code with a restricted audience while it's being worked on, but prevent the new version(s) from being used outside of that audience until the library developer is ready.