Contributing¶
Small, reproducible reports are a good starting point. Include the release or commit, operating system, client version, a minimal query, expected result, and actual result. For comparisons, state which upstream version you tested.
Useful areas for the next preview¶
Reproduce the install flow on a clean system, test real workloads, investigate the documented performance outliers, or contribute physical iOS evidence. Please keep results and limitations explicit; a successful build does not establish runtime compatibility.
Development workflow¶
main is the integration branch. v1.5-variegata is the current maintenance
and release branch, matching DuckDB's 1.5 series. Tags and package versions
match the compatibility target (v1.5.6 / 1.5.6). Preview status is separate.
Other version-family branches are added when their corresponding ports are
maintained. The existing
amirbaron/rust-duckdb-port development branch uses pull requests targeting
main. External contributors can open pull requests from topic branches in
their forks. Documentation deploys from main, without an extra site branch.
CI covers focused regression, source builds, documentation, and packaging checks. The full historical SQL/client/performance qualification is larger than the per-change CI suite. Required release checks must run on the artifact being released, with provenance and exceptions retained.