[VL] Fix release packaging and rewrite the release guide - #12761
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Velox release packaging flow to produce ASF-compliant binary tarballs and substantially rewrites the Velox release guide to document the end-to-end RC/vote/publish process.
Changes:
- Extend
package-release.shto package Spark 4.1 artifacts and includeLICENSE/NOTICEinside each binary tarball (sourced fromLICENSE-binary/NOTICE-binary). - Rewrite/expand
docs/developers/HowToRelease.mdwith pre-release checks, CI-based build guidance, and more detailed voting/publishing steps.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| docs/developers/HowToRelease.md | Expanded and reorganized the Velox release guide, adding pre-release checks and more detailed RC/vote/publish instructions. |
| dev/release/package-release.sh | Fixes/improves binary packaging (top-level dir + LICENSE/NOTICE), adds Spark 4.1 packaging, and fails fast on missing prerequisites. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+29
to
+30
| VELOX_REPO=https://github.com/IBM/velox.git | ||
| VELOX_BRANCH=branch-1.7-dft |
Member
Author
There was a problem hiding this comment.
This is just an example for the release steps.
zhouyuan
approved these changes
Aug 14, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.
Suppressed comments (1)
docs/developers/HowToRelease.md:254
- The command uses
gpg --send-key, which isn’t a valid GnuPG option (it should be--send-keys). Also, uploading by email/UID can be ambiguous; it’s clearer to send the actual key id shown by--list-keys.
gpg --list-keys --keyid-format SHORT <asf-id>@apache.org
gpg --keyserver keyserver.ubuntu.com --send-key <asf-id>@apache.org
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes are proposed in this pull request?
Documents the release process in more detail, so that a release manager — particularly one running it for the first time — can follow it end to end without reconstructing the missing steps.
How was this patch tested?
Tested in the release process.
Was this patch authored or co-authored using generative AI tooling?
Claude Opus 5 helped improve the wording.