[VOTE] Batch backport release candidates for v3.0–v9.0 #8179
Closed
Xuanwo
started this conversation in
Release Vote
Replies: 4 comments
|
+1 |
0 replies
|
+1 |
0 replies
|
+1 |
0 replies
Final resultThe batch vote passed with three binding PMC +1 votes and no vetoes. All six stable releases have been published and independently verified:
Verification covered signed annotated tags, non-prerelease GitHub Releases, six wheels per PyPI version, Maven POM/JAR artifacts, every versioned workspace crate plus the top-level lance crate, and successful BSR publishing. Publishing recovery notes:
v5.0 is intentionally excluded: v5.0.0 never completed a stable release, only beta/RC artifacts existed, and the line has been superseded. v5.0.0-rc.2 remains immutable prerelease history. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Batch backport release vote
This Discussion covers six independently votable stable release candidates containing the same two corruption-safety fixes:
VariableFullZipDecoder::unzipThe fixes were backported by #8152, #8153, #8155, #8156, #8157, and #8158. Each candidate is immutable: the release link and commit below identify the exact source being voted on.
Candidates
release/v3.06d7031brelease/v4.00f42222release/v6.124ecc6brelease/v7.19f1d239release/v8.0bef286frelease/v9.0052eb9eAll 18 in-scope artifact workflows completed successfully. All Python candidates are visible in the Fury index, and all Java candidate POMs are visible in Maven Central.
Testing
Test the release lines relevant to you and scope your vote accordingly.
Python example (use the PEP 440-normalized version for the selected candidate):
pip install --pre --extra-index-url https://pypi.fury.io/lance-format/ "pylance==9.0.1rc1"Java example:
Rust example:
Voting
Each candidate is an independent stable-release decision. Cast each vote as a top-level comment, not as a reply. Examples:
+1 (binding): all candidates+1 (binding): v8.0.1-rc.1, v9.0.1-rc.10: v4.0.2-rc.1-1 (binding): v6.1.0-rc.2 — <reason>An unscoped vote applies to all candidates. Each candidate requires 3 binding +1 votes from PMC members and no valid binding
-1veto. A-1vote must include justification. Non-binding votes are welcome.Although patch releases have no minimum voting period, this batch uses one common window because it also includes major/minor stable releases. The vote will remain open until at least 2026-08-06 10:00 UTC (2026-08-06 03:00 PDT). Eligible candidates may then be promoted independently.
If one candidate needs a replacement RC, only that release line needs renewed confirmation; unaffected candidates may proceed after the common window.
Scope
release/v5.0is intentionally excluded from this vote.release/v6.0andrelease/v7.0are intentionally excluded in favor ofrelease/v6.1andrelease/v7.1.After the vote, approved candidates will be promoted directly on their release branches and their stable artifacts will be verified independently.
Why v5.0 is excluded
v5.0.0never completed a stable release: only beta and RC tags exist, the v5.0.0-rc.1 vote received no votes, and no stable Python, Java, or Rust artifacts were published. The release line has since been superseded by later major versions. Publishing v5.0.0-rc.2 now would be a delayed first stable v5 release rather than a backport release for an established stable version, so it is outside this vote. The v5.0.0-rc.2 prerelease remains available as an immutable historical candidate.All reactions