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.

Sign up for GitHub

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

Jump to bottom

Breaking changes to properly justify a 2.0 release #2128

Open
denelon opened this issue Apr 27, 2022 · 3 comments
Open

Breaking changes to properly justify a 2.0 release #2128

denelon opened this issue Apr 27, 2022 · 3 comments
Labels
Breaking-Change This is potentially a breaking change for a future major version Issue-Feature This is a feature request for the Windows Package Manager client.
Milestone
2.0-Client

Comments

@denelon
Copy link
Contributor

denelon commented Apr 27, 2022 •
edited
Loading

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.

Proposed technical implementation details

No response
@denelon denelon added the Issue-Feature This is a feature request for the Windows Package Manager client. label Apr 27, 2022
@ghost ghost added the Needs-Triage Issue need to be triaged label Apr 27, 2022
@denelon denelon removed the Needs-Triage Issue need to be triaged label Apr 27, 2022
@denelon denelon mentioned this issue Jun 7, 2022
Closed
@Trenly
Copy link
Contributor

Trenly commented Aug 3, 2022

I was looking through the list of issues and found this one which could be a consideration for a 2.0 release or to be dropped -

@denelon denelon mentioned this issue Nov 3, 2022
Open
2 tasks
This was referenced Feb 15, 2023
Open
Open
@denelon denelon added this to the v2.0-Client milestone Feb 15, 2023
@denelon
Copy link
Contributor Author

denelon commented Mar 5, 2023

Additional asks in:

@denelon denelon mentioned this issue May 31, 2023
Open
@Trenly
Copy link
Contributor

Trenly commented Jun 16, 2023

[Policy] Breaking-Change

@microsoft-github-policy-service microsoft-github-policy-service bot added the Breaking-Change This is potentially a breaking change for a future major version label Jun 16, 2023
@possumdoe possumdoe mentioned this issue Feb 6, 2024
Closed
@Trenly Trenly mentioned this issue Oct 11, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Breaking-Change This is potentially a breaking change for a future major version Issue-Feature This is a feature request for the Windows Package Manager client.
Projects
None yet
Milestone
2.0-Client
Development

No branches or pull requests
2 participants
@Trenly @denelon