lance-format / lance-format/lance
Update forward compatibility tests to always use relatively recent versions
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.1k
- Forks
- 852
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 272
Description
Currently the forwards compatibility tests are targeting a random smattering of hard-coded versions. In theory the entire range of released versions is our target surface. However, since that is likely infeasible, we should focus our efforts. One of the most common scenarios will be users that have A/B style rollouts. In that case we want to make sure we are forwards compatible with relatively recent versions. Perhaps we should automate the forwards compatibility testing so that it always tests against versions N-1, N-2 (or some small range of recent versions)?
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
Start by locating the forward compatibility tests and the hard-coded version list they currently target. Determine how released versions are identified, then define a recent-version range such as N-1 and N-2 and verify that the tests consistently run against it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100