You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Takes the RC number as input (e.g. `0.42.0-RC1`)
Checks out both SVN paths (`dist/dev/incubator/burr/` and `dist/release/incubator/burr/`)
Moves artifacts from dev to release, renaming to remove RC suffix
Removes old releases from `dist/release` (ASF policy: only latest)
Commits to SVN
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
@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?
Activity
andreahlert commentedon Mar 30, 2026
@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?
Haricharanpanjwani commentedon Apr 19, 2026
@andreahlert I can work on this issue.
skrawcz commentedon Apr 20, 2026
@andreahlert rather than copy it moves the artifacts (I updated the ticket).
Haricharanpanjwani commentedon May 2, 2026
@skrawcz @andreahlert @pjfanning can you review the PR #749
github-actions commentedon May 20, 2026
@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).
Haricharanpanjwani commentedon Jun 1, 2026
PR is updated: #749, can I get a review on it?
andreahlert commentedon Jun 2, 2026
Just made a few adjustments. Approved @elijahbenizzy can you take a second vote on that?