What's on the Roadmap? #2063

Many people have asked questions about the roadmap and how we prioritize the features we are working on. In the spirit of transparency, I'll share our philosophy.

We have a few competing priorities and limited resources. In general, we use Milestones to give a hint as to what we're working on, and when the milestone could be "code complete".

Note: The dates and scope are aspirational. These should not be treated as a commitment.

A numbered milestone represents the next features we're targeting in the next stable release. The V.Next milestone is a placeholder for some asks we're considering in a near milestone. Work items will be moved in and out as time and resources allow.

In some cases, we have strategic work taking priority. This happened with support for Apps in the Microsoft Store. Another area is the work to integrate with Intune. Others may come up in the future.

• #545 (Iterated on and released as stable in Windows Package Manager 1.1)
• #215

The next set of work items to be prioritized are based on "impact". These are items that would substantially improve capabilities. These items would be things like support for portable applications, dependencies, package pinning, and channels.

• #140
• #147
• #163
• #182
• #221
• #476

Last, but certainly not least are features and bugs with the most 👍 indicating community support.

• Features
• Bugs

Note: Feel free to add your thumbs up to help raise visibility. Please be respectful and don't add comments like "I want this too". Many users subscribe to Issues and would receive e-mail notifications. If you believe you have identified a unique scenario not captured in the Issue, adding a clear scenario with the impact is helpful.