potiuk opened a new pull request, #65644: URL: https://github.com/apache/airflow/pull/65644
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: 1. Reads the checked lines from the previous RC's issue. 2. For each unchecked line in the new RC's issue, pre-checks it if any PR number on that line was already verified in the previous RC — matching works across \`[v3-2-test]\` backport PRs that reference the original main-branch PR number on the same line (\`... (#64935) (#65001)\`). 3. Posts a comment on the new issue explaining what was carried over. 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 - [X] N/A — doc-only. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Opus 4.7 (1M context) Generated-by: Claude Opus 4.7 (1M context) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
