airflow-ctl release: carry over checked boxes from the previous RC#65644
Merged
potiuk merged 1 commit intoapache:mainfrom Apr 22, 2026
Merged
airflow-ctl release: carry over checked boxes from the previous RC#65644potiuk merged 1 commit intoapache:mainfrom
potiuk merged 1 commit intoapache:mainfrom
Conversation
When cutting a follow-up RC, items that testers already verified on the previous RC should be pre-checked so they do not retest unchanged fixes. Add a step to the airflow-ctl release doc that takes a diff of checked boxes between the previous and current RC's testing-status issues and pre-checks the matching items in the new issue (matching works across v3-2-test backport PRs that reference the original main PR number on the same line). Caught while running 0.1.4rc3 — 7 items from rc2 carried over; without the carry-over, all of those testers would have had to re-verify.
potiuk
requested review from
bugraoz93,
jedcunningham,
jscheffl,
shahar1 and
vincbeck
as code owners
boring-cyborg
Bot
added
area:dev-tools
backport-to-v3-2-test
bugraoz93
approved these changes
Apr 22, 2026
Contributor
bugraoz93
left a comment
bugraoz93
left a comment
There was a problem hiding this comment.
Nice, I generally copied old content as it was really a hassle to create these manually for a while :D Great to have it in the doc
Contributor
Backport successfully created: v3-2-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
github-actions Bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Apr 22, 2026
…pache#65644) When cutting a follow-up RC, items that testers already verified on the previous RC should be pre-checked so they do not retest unchanged fixes. Add a step to the airflow-ctl release doc that takes a diff of checked boxes between the previous and current RC's testing-status issues and pre-checks the matching items in the new issue (matching works across v3-2-test backport PRs that reference the original main PR number on the same line). Caught while running 0.1.4rc3 — 7 items from rc2 carried over; without the carry-over, all of those testers would have had to re-verify. (cherry picked from commit f74bcad) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
aws-airflow-bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Apr 22, 2026
…pache#65644) When cutting a follow-up RC, items that testers already verified on the previous RC should be pre-checked so they do not retest unchanged fixes. Add a step to the airflow-ctl release doc that takes a diff of checked boxes between the previous and current RC's testing-status issues and pre-checks the matching items in the new issue (matching works across v3-2-test backport PRs that reference the original main PR number on the same line). Caught while running 0.1.4rc3 — 7 items from rc2 carried over; without the carry-over, all of those testers would have had to re-verify. (cherry picked from commit f74bcad) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk
added a commit
that referenced
this pull request
Apr 22, 2026
…65644) (#65697) When cutting a follow-up RC, items that testers already verified on the previous RC should be pre-checked so they do not retest unchanged fixes. Add a step to the airflow-ctl release doc that takes a diff of checked boxes between the previous and current RC's testing-status issues and pre-checks the matching items in the new issue (matching works across v3-2-test backport PRs that reference the original main PR number on the same line). Caught while running 0.1.4rc3 — 7 items from rc2 carried over; without the carry-over, all of those testers would have had to re-verify. (cherry picked from commit f74bcad) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
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
2 participants
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.
When cutting a follow-up RC (rcN after rcN-1 was voted down), items that testers already verified on rcN-1 should be pre-checked in the new testing-status issue — otherwise testers waste time retesting unchanged fixes, and cross-RC progress is hard to see.
Add a carry-over step to the airflow-ctl release doc right after the testing-status issue is created. It:
Caught while running 0.1.4rc3 — 7 items from rc2 (#65497) carried over into rc3 (#65643) with this procedure. Without it, all 7 testers would have had to retest unchanged backports.
Test plan
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Opus 4.7 (1M context) following the guidelines