Jeff Handley 

On November 12, 2014, as part of the Visual Studio 2015 Preview release, we released NuGet 3.0 Preview. This is a big release for us (albeit a preview), and we’re excited to start getting feedback on our changes.
Visual Studio 2012+
This NuGet 3.0 Preview is included in Visual Studio 2015 Preview.

As we work on the designs for getting NuGet in the platform, it has become clear that NuGet needs better support for carrying arbitrary artifacts in packages and exposing them for consumption after the initial package installation.
Conventional Manifests
Since NuGet’s initial release,

As NuGet continues to gain momentum, more Microsoft teams have been seeking to install NuGet packages from their Visual Studio tooling. This began with ASP.NET, where NuGet was born, when project templates started coming with pre-installed NuGet packages. More recently, we’ve heard of teams all across Microsoft with tooling gestures that result in NuGet packages being installed.

As we work on some big changes for NuGet 3.x, we’re finding that we’re at a crossroads: Should we use .NET 4.5 and improve our Visual Studio UI using new features available in Visual Studio 2012, Visual Studio 2013, and Visual Studio “14”;

Updated Sept. 2015: Our roadmap and requirements have changed and we have yet to implement these features as of NuGet v3.2. We are tracking this issue on GitHub. Please track this issue to follow our progress.
We adopted Semantic Versioning (SemVer) in NuGet 1.6.

The Warehouse is Dead, Long Live the Warehouse!
Back in June, we blogged that our package statistics were full of lies. We made a fix and expected reports to become correct on June 26th. When June 26th came and went though,

Today marks an important milestone for Building NuGet 3.x; we’ve published a NuGet 3.0 CTP1 build of our Visual Studio extension. This preview release represents a few months of code refactoring and server-side architecture now being utilized by the client code.

As part of Building NuGet 3.x, we have been working on a significant re-architecture of NuGet.org. Progress has been steady and we are starting to see a return on investment. In this post, we’ll compare the legacy architecture to where we’ll be in the near future.

We’ve recently found ourselves answering the same question repeatedly: How do you monitor nuget.org? If you too are interested, here are the details.
Monitoring Approaches
We have two approaches for monitoring the gallery:

From the outside, checking HTTP endpoints that indicate public-facing service interruptions
From the inside,

Lies, Damned Lies, and Package Statistics
We’ve been getting reports about package download statistics being inconsistent with packages’ overall download counts and people have asked us which numbers to believe. We’ve investigated the inconsistencies and found that due to a very subtle bug,