-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Dependencies
Use Case
Kerberos and zstd should be added to the peer optional dependency specification in our driver's package.json. We could do this in a feature bump of v5 as long as the version numbering was permissive enough.
zstd has not yet had a major version beyond 1 so we can allow ^1.0.0 and it shouldn't break existing workflows
kerberos would have to specify ^1.0.0 || ^2.0.0 in order to avoid adding a restriction that wasn't previously present.
User Impact
*What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?
Dependencies
- upstream and/or downstream requirements and timelines to bear in mind
Unknowns
- questions that need to be answered to determine implementation
Acceptance Criteria
Implementation Requirements
Testing Requirements
- unit test, spec test sync, etc
Documentation Requirements
- DOCSP ticket, API docs, etc
Follow Up Requirements
- additional tickets to file, required releases, etc