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

[storage][needs-breaking-change] issues for which fixes need to introduce breaking changes #10793

Closed
ljian3377 opened this issue Aug 24, 2020 · 2 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Storage Storage Service (Queues, Blobs, Files)

Comments

@ljian3377
Copy link
Member

ljian3377 commented Aug 24, 2020

Keep track of those issues where the right fix will introduce breaking changes. Hopefully we can get them right when it comes to the next major release.

FIXED
1. TelemetryPolicyFactory remove the first spcae in userAgentPrefix.

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Aug 24, 2020
@ljian3377 ljian3377 added Storage Storage Service (Queues, Blobs, Files) and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Aug 24, 2020
@ljian3377 ljian3377 added this to the Backlog milestone Aug 24, 2020
@jiacfan jiacfan removed their assignment Aug 27, 2020
@ljian3377
Copy link
Member Author

  1. File: Change the accessPolicy in SignedIdentifier's fields and itself to optional
    Fix for issue #11505 #11527

@ljian3377 ljian3377 added the Client This issue points to a problem in the data-plane of the library. label Oct 21, 2020
@XiaoningLiu XiaoningLiu removed their assignment Oct 21, 2020
@ljian3377 ljian3377 changed the title [storage] fixes that introduce breaking changes [storage] issues for which fixes need to introduce breaking changes Oct 24, 2020
@ljian3377 ljian3377 changed the title [storage] issues for which fixes need to introduce breaking changes [storage][needs-breaking-change] issues for which fixes need to introduce breaking changes Oct 28, 2020
Copy link

Hi @ljian3377, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 20, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Mar 20, 2024
@xirzec xirzec removed this from the Backlog milestone May 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

No branches or pull requests

5 participants