Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plan for NuGet in 2023 #12407

Closed
JonDouglas opened this issue Feb 3, 2023 · 12 comments
Closed

Plan for NuGet in 2023 #12407

JonDouglas opened this issue Feb 3, 2023 · 12 comments
Assignees
Labels
Type:Tracking This issue is tracking the completion of other related issues.

Comments

@JonDouglas
Copy link
Contributor

JonDouglas commented Feb 3, 2023

Today we are excited to share with you the plan for NuGet and NuGet.org. This issue contains summary of the plan for the year and acts as a place for you to leave feedback.

This plan is a collection of input from many stakeholders and outlines where we intend to invest our time in NuGet and NuGet.org.

IMPORTANT
This plan is not a commitment; it will evolve as we continue to learn throughout the release. Some things that are not currently planned for NuGet may get pulled in. Some things currently planned may even be pushed out.

General information

NuGet has a major release following NuGet 6.4 and is currently scheduled for release in November 2023 at the same time as .NET 8.

NuGet will align with the .NET support policy and will therefore be a long-term support (LTS) release.

NuGet.org does not currently follow any specific schedule and releases features & bug fixes regularly throughout the year.

Breaking changes

NuGet may contain a small number of breaking changes as we continue to evolve NuGet with the .NET platform. Our goal is to minimize breaking changes as much as possible to keep you productive when upgrading. You'll be able to find them at the .NET 8 Breaking Changes.

Themes

The large investments in NuGet are the following themes:

Highly Requested Features

As always, a major input into our planning process comes from votes (👍) for features on GitHub.

These features are areas we are actively engaged in with regards to designing, implementing, and polishing the respective experiences for.

Security

Tooling

Season of Giving

NuGet Gallery

.NET Platforms and Ecosystem

Much of the work planned for NuGet involves improving the package management experience for .NET across different platforms and ecosystem. This involves work in NuGet to ensure a great experience across .NET technologies.

Migrating to .NET

NuGet has always supported many scenarios for package management. In our continued efforts to help you migrate to the latest version of .NET, we will be working on improvements to the Upgrade Assistant and core package management experiences to help you migrate your project to use the latest version of NuGet.

Performance

With each new release of NuGet & Visual Studio comes a plethora of performance improvements when restoring NuGet packages, managing project dependencies, and browsing for the next great package to include in your solution. We will continue to invest time to improve your experiences every .NET & Visual Studio release.

Feedback

Your feedback is important to us. The best way to indicate the importance of an issue is to vote (👍) for that issue on GitHub and Visual Studio Developer Community. We use this data to help us with our regular planning so we can work on the things that matter most to you.

Please comment on this issue if you believe we are missing something that is critical for NuGet, or are focusing on the wrong areas. Give us a little bit of context as to why you believe so and feel free to upvote each other's comments to help us make changes to our future plans.

Huge thanks to @ajcvickers and the Entity Framework Core team for a wonderful format and forum to discuss product plans in OSS. 🎉

Last year's plan can be found in #11571

@JonDouglas JonDouglas self-assigned this Feb 3, 2023
@ghost
Copy link

ghost commented Feb 3, 2023

@JonDouglas Issue is missing Type label, remember to add a Type label

@ghost ghost added the missing-required-type The required type label is missing. label Feb 3, 2023
@ghost
Copy link

ghost commented Feb 3, 2023

@JonDouglas Issue is missing Type label, remember to add a Type label

@JonDouglas JonDouglas pinned this issue Feb 3, 2023
@JonDouglas JonDouglas added the Type:Tracking This issue is tracking the completion of other related issues. label Feb 3, 2023
@ghost ghost removed the missing-required-type The required type label is missing. label Feb 3, 2023
@marco-carvalho
Copy link

@JonDouglas any chance of #4387 being prioritized?

@JonDouglas
Copy link
Contributor Author

JonDouglas commented Feb 13, 2023

@marco-carvalho I believe that one and #12015 are related. Can you check if that's the case? Will add them both until we de-dupe.

@Varorbc
Copy link

Varorbc commented Mar 9, 2023

Could you please include #12473 in the plan?

@JonDouglas
Copy link
Contributor Author

@Varorbc we will triage this issue, but right now it is too new to include in the plan although it is an excellent suggestion.

@zlsmith86
Copy link

Can dotnet/sdk#9500 be included as well?

@baronfel
Copy link

baronfel commented Mar 30, 2023

@zlsmith86 dotnet/sdk#9500 (and dotnet tools generally) is owned by the SDK team, not the NuGet team, and so isn't in scope for NuGet's 2023 plan. We (the SDK team) are actively working on it though - see the linked PR from that issue.

@smarts
Copy link

smarts commented Jun 6, 2023

Can #1851 and #6437 be handled together? Seems like the problems are fairly similar, no?

It's not clear to me why 6437 is not categorized under Security, and why it's not prioritized higher. It's got more 👍🏼 votes than nearly all of the items in that category.

@zivkan
Copy link
Member

zivkan commented Jun 6, 2023

@smarts I think that #12539 is a better solution than #6437, at least for CI scenarios. It should also be much easier to implement. Unfortunately I have too many other higher priority things to have worked on it myself yet, but I think it might be simple enough for someone else to contribute, if someone wants to try before I, or someone else in the team, finds time to do it ourselves.

@smarts
Copy link

smarts commented Jun 30, 2023

Got it, thank you! 🙂

@JonDouglas
Copy link
Contributor Author

JonDouglas commented Nov 25, 2023

Hi friends,

In preparation for the next year, I'm going to close this plan. We made significant progress on many fronts. Not everything is documented but here is a taste of what was done besides what was closed in various issues above. There are some issues that still need closing as their functionality has shipped or will be shipped soon.

Releases:

Feature Blogs:

NuGet Tooling:

NuGet Gallery:

Epics:

New/Closed Proposals:

To help us for next year, please go through our issues/prs on all our https://github.com/NuGet/Home#repos-and-projects and please upvote, comment, and contribute where you think is appropriate!

Thank you for all your help in making this year great.

@JonDouglas JonDouglas unpinned this issue Nov 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type:Tracking This issue is tracking the completion of other related issues.
Projects
None yet
Development

No branches or pull requests

7 participants