microsoft / microsoft/winget-cli
Breaking changes to properly justify a 2.0 release
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Description of the new feature / enhancement
In the spirit of semantic versioning, we want to identify issues that are potentially breaking changes to consider for a future 2.0 release. This list is not a commitment for what would be in a 2.0 release, but rather to identify candidates. This list may be amended over time, and any issues not taken into a 2.0 release should be moved to a similar Issue to identify a future 3.0 release.
- #715
- microsoft/winget-cli/discussions/2106
- microsoft/winget-cli/discussions/2112
- https://github.com/microsoft/winget-cli/issues/2972
Proposed technical implementation details
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the candidate issues and discussions listed in #2128, including #715, discussions/2106 and 2112, and issue #2972. Clarify which breaking changes belong in a future 2.0 release and document the agreed candidate list; completion is not defined until the project decides how this tracking issue should be maintained.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100