Versioning and compatibility
Open
- Dominant language
- Thrift
- Stars
- 7
- Forks
- 1
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 1
Description
We had a brief conversation about versioning and compatibility between the native clients and the webview, so I thought we should get something in writing about how we're going to handle changes to the WebView / Native Thrift API over time.
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the issue body and its seven-comment conversation to understand the unresolved versioning and compatibility concerns between the WebView and native clients. Confirm the expected scope with maintainers, then document an agreed approach for handling changes to the WebView/native Thrift API; done means the policy is written and the compatibility expectations are clear.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100