Skip to content

ci: vote and announcement email tooling #719

Closed

Description

@andreahlert

Part of #715

Problem

Vote emails, result emails, and release announcements are composed manually. The format varies between releases and it is easy to forget required information (SVN links, KEYS file link, changelog, etc.).

Solution

Add a lightweight email tooling script that:

  1. Generates vote email from a Jinja2 template, pre-filled with:
    • Version and RC number
    • Links to SVN artifacts, PyPI RC package, and KEYS file
    • Changelog summary
    • Voting deadline (72h from now)
  2. Generates result email from a template, with vote tally
  3. Generates announcement email from a template
  4. Outputs to stdout (or copies to clipboard) for the release manager to send

Acceptance criteria

  • Vote email template (`scripts/templates/vote_email.j2`)
  • Result email template (`scripts/templates/result_email.j2`)
  • Announcement email template (`scripts/templates/announce_email.j2`)
  • CLI command to generate each: `python scripts/apache_release.py vote-email --version 0.43.0 --rc 1`

Activity

  1. andreahlert commented on Mar 30, 2026

    @andreahlert
    CollaboratorAuthor

    @skrawcz low priority but figured I'd file it. _generate_vote_email() already covers the vote template, but we don't have result or announcement templates. thinking we could add those plus a CLI entry point so the whole email flow is python apache_release.py vote-email, result-email, announce-email. would that be useful for you or is copy-paste fine?

  2. hussain-s commented on Apr 17, 2026

    @hussain-s
    Contributor

    Please assign to me I can work on this one

  3. hussain-s commented on Apr 18, 2026

    @hussain-s
    Contributor

    Pull request for the issue 719 is in following PR.

  4. hussain-s commented on Apr 19, 2026

    @hussain-s
    Contributor

    Revision 2 submitted after addressing the github copilot comment

  5. hussain-s commented on Apr 28, 2026

    @hussain-s
    Contributor

    Revision 3 submitted after addressing the the github copilot comment.

  6. github-actions commented on May 13, 2026

    @github-actions

    @hussain-s, this issue has been inactive for 14 days.
    Are you still working on it? Drop a comment to let us know.

    If there is no update within 7 days, the assignment will be removed
    so someone else can pick it up
    (per the assignment policy).

  7. github-actions commented on May 27, 2026

    @github-actions

    @hussain-s, this issue has been inactive for 14 days.
    Are you still working on it? Drop a comment to let us know.

    If there is no update within 7 days, the assignment will be removed
    so someone else can pick it up
    (per the assignment policy).

  8. hussain-s commented on Jun 7, 2026

    @hussain-s
    Contributor

    PR Is merged we can close the issue

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

Metadata

Metadata

Assignees

Labels

area/ciWorkflows, build, release scriptskind/featureNet-new functionalitypriority/lowNice-to-have, backlog

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions