Skip to content

Conversation

@bobbai00
Copy link
Contributor

@bobbai00 bobbai00 commented Dec 11, 2025

What changes were proposed in this PR?

Update release candidate workflow and vote email template based on Apache mentor feedback:

  1. KEYS URL: Changed to https://downloads.apache.org/incubator/texera/KEYS (official location, auto-synced from release)
  2. Tarball naming: Removed 'rc' suffix from filename (apache-texera-X.Y.Z-incubating-src.tar.gz). RC number remains in directory name.
  3. Vote email: Simplified verification instructions (removed wget commands), added convenience binaries section

Any related issues, documentation, discussions?

Fixes #4127

How was this PR tested?

Template and workflow changes reviewed manually.

Was this PR authored or co-authored using generative AI tooling?

Co-authered with Claude Code (Claude Opus 4.5)

- Use downloads.apache.org/incubator/texera/KEYS as official KEYS URL
- Remove 'rc' suffix from tarball filename (keep RC in directory name)
- Simplify verification instructions (remove wget commands)
- Add convenience binaries section to vote email template

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@github-actions github-actions bot added ci changes related to CI docs Changes related to documentations labels Dec 11, 2025
@bobbai00 bobbai00 changed the title chore: update release workflow per Apache mentor feedback chore: update release workflow to comply with Apache release practice Dec 11, 2025
@bobbai00 bobbai00 self-assigned this Dec 11, 2025
@bobbai00 bobbai00 requested a review from pjfanning December 11, 2025 02:37
Copy link
Contributor

@aglinxinyuan aglinxinyuan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!


== Checklist for Reference ==
Docker images (tag: ${VERSION}):
- https://hub.docker.com/r/apache/texera-workflow-compiling-service/tags?name=${VERSION}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

[ ] +1 Approve the release
[ ] 0 No opinion
[ ] -1 Disapprove the release (please provide the reason)
[ ] -1 Disapprove the release (please provide reason)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the reason is better

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@pjfanning
Copy link
Member

Will the jars be pushed to repository.apache.org for review?

@bobbai00
Copy link
Contributor Author

Will the jars be pushed to repository.apache.org for review?

Maybe we can discuss this in the release discussion email thread. I will initiate the thread soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci changes related to CI docs Changes related to documentations

Projects

None yet

Development

Successfully merging this pull request may close these issues.

release workflow and email template need to be improved

3 participants