Skip to content

ci: add RC promotion script (dev -> release) #717

Closed

Description

@andreahlert

Part of #715

Problem

After an RC passes the vote, promoting artifacts from `dist/dev` to `dist/release` is done manually via SVN commands. This is error-prone (wrong paths, forgetting to remove the RC suffix, missing artifacts) and undocumented beyond tribal knowledge.

Solution

Add a `promote` subcommand to `scripts/apache_release.py` (or a separate script) that:

  1. Takes the RC number as input (e.g. `0.42.0-RC1`)
  2. Checks out both SVN paths (`dist/dev/incubator/burr/` and `dist/release/incubator/burr/`)
  3. Moves artifacts from dev to release, renaming to remove RC suffix
  4. Removes old releases from `dist/release` (ASF policy: only latest)
  5. Commits to SVN
  6. Prints the PyPI upload command for the final release

Acceptance criteria

  • Single command to promote a voted RC
  • Validates that all expected artifacts exist before promoting
  • Handles the incubating -> TLP transition (path changes)
  • Dry-run mode that shows what would happen without committing

Activity

  1. added
    area/ciWorkflows, build, release scripts
    priority/highAffects many users, needs action within weeks
    on Mar 30, 2026
  2. andreahlert commented on Mar 30, 2026

    @andreahlert
    CollaboratorAuthor

    @skrawcz since you've been doing the RC promotions manually, curious what your current steps look like. I want to make sure the script covers everything you already do, not just what I think the process is. also @pjfanning any gotchas from other projects when automating the dev -> release SVN move?

  3. Haricharanpanjwani commented on Apr 19, 2026

    @Haricharanpanjwani
    Contributor

    @andreahlert I can work on this issue.

  4. skrawcz commented on Apr 20, 2026

    @skrawcz
    Contributor

    @andreahlert rather than copy it moves the artifacts (I updated the ticket).

  5. Haricharanpanjwani commented on May 2, 2026

    @Haricharanpanjwani
    Contributor

    @skrawcz @andreahlert @pjfanning can you review the PR #749

  6. github-actions commented on May 20, 2026

    @github-actions

    @Haricharanpanjwani, this issue has been inactive for 18 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. Haricharanpanjwani commented on Jun 1, 2026

    @Haricharanpanjwani
    Contributor

    PR is updated: #749, can I get a review on it?

  8. andreahlert commented on Jun 2, 2026

    @andreahlert
    CollaboratorAuthor

    Just made a few adjustments. Approved @elijahbenizzy can you take a second vote on that?

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

Metadata

Metadata

Labels

area/ciWorkflows, build, release scriptskind/featureNet-new functionalitypriority/highAffects many users, needs action within weeks

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions