Implement staged/transactional bulk uploads

[blowdart]

Currently Patch Tuesday is painful. We kick off the upload and each package trickles live, so one 1.1.3 package would be available after upload, without its dependencies being available yet.

We would like the ability to upload our 300+ packages at some point before release and then, with a single click, mark the entire set as available.

[skofman1]

Sounds a lot like the staging feature. It's in our backlog.

[karann-msft]

Another thing to consider
.nupkg and .snupkg could be uploaded together and fail publication together

[dotMorten]

This would be a huge value-add for us as well. We generally want to go live at a specific coordinated time, but have often been hit by last-minute validation errors, causing a mad scramble to try and fix the issue, before re-uploading. I'd prefer I could upload all my packages 1-2 weeks in advance, take our time to get the readme description right, tweak URLs as they are getting ready, get full verification that these packages are "valid" and will publish, and the only difference between this and unlisted, is that they are not accessible, and they are replaceable. The replaceable feature is important as well, as we might in those 1-2 weeks find a showstopper, and want to re-upload the package without having to increase the version number.

Here's the simplest workflow I suggest:

1. Upload the package. Instead of checking the "unlist" option, you get a "stage" option.
2. Package runs through full validation, and is ready to go - but not accessible.
3. A new list of "staged" packages, in addition to the "unlisted" section, where not-yet published packages are listed, each with a "publish" button.
4. Package can be modified/replaced/deleted all up until the point where I switched a package from staged to published.

Nice-to-haves, but not MVP:

• Upload group of packages in bulk.
• Set a time/date for automatic publish.
• Publish entire group of packages in one click (or auto-publish dependencies of the package you published).

[RealDotNetDave]

I think we need everything that @dotMorten mentioned. For me, I don't have hundreds, just a handful. I'd like to be able to open the file explorer, select the packages then press Submit to upload them. At my new job, we will in the future, have a lot of packages to upload.

Maybe we should have a "Publish to NuGet" option in Visual Studio.

[dotMorten]

@RealDotNetDave its fairly easy to do bulk upload from commandline though. (As long as the tool will be updated to support pushing to staging rather than publish)