• Roadmap
• How to use ZenHub

• Enable repeatable builds for PackageReference based projects
• Full Support of LSL
• Package Sources Analyzer
• NuGet Restore Manager
• Account Deletion Workflow
• Search by Package Type and Query Language Surfacing
• Command option consistency
• Secret Rotation
• Support dotnet add\update\del packageref
• Package README.md support

• Organizations on NuGet.org
• 2 Factor Auth for NuGet.org sign in
• NuGetizer 3000
• NuGet Upgrader
• Converting Extension SDKs into NuGet Packages
• Supporting Package Reference in UWP WPF WinForms and Classic Libraries
• Enhanced package upload workflow
• ToolsReference and Multi TFM Support in NuGet UI
• Transitive Warning Properties

• SemVer 2.0.0 - client-side
• SemVer 2.0.0 - server-side
• Replication API
• NuGet Package Identity Verification

• NuGet Package Download Plugin
• Enable .NET Core 2.0 projects to work with .NET Framework 4.6.1 compatible packages
• Improved NuGet errors warnings
• Filter OData query requests
• Multiple API Keys
• Batch Events
• Aggressive No Caching Mode
• Package Type [Packing]
• Add Clear Cache button to VS Package Manager Console
• Support nuget push command in dotnet CLI
• Support nuget locals command in dotnet CLI
• Restore target
• Adding nuget pack as a msbuild target
• Issue server-side warnings to NuGet client

• Sep 2, 2015 - Csproj to Xproj
• Aug 21, 2015 - UI design,
• Aug 18, 2015 - Lock file
• Aug 12, 2015 - MsBuild/project.json

• Spec Template

The NuGet Team Wiki will be primarily used for 3 things:-

1. Documenting and updating the product roadmap
2. Design meeting notes
3. NuGet product specifications

The product roadmap is constantly evolving document that will reflect the team's priorities and the needs of the community for the next one year or so. If you see any items missing that you strongly believe needs to be part of the roadmap, open an issue and let us know.

We will create design discussion summaries for each design discussion and create a wiki page and a corresponding issue with the Discussion label in the Future milestone. These issues will stay open for a relatively long amount of time, and are for free and open discussion. They can turn into actionable issues, or remain in discussion state.

Product specifications enable the team to put forward ideas, get the discussion going within the team and the community and finally have a well thought out proposal ready for implementation. This will generally only be used by the NuGet team. As always, the community can always open issues to put forward their proposals. Provided it aligns with our priorities, roadmap and vision for NuGet, the NuGet team will work with you to formalize that into a product specification. Check this page to get an overview of how to write and review your spec.