potiuk commented on PR #31830: URL: https://github.com/apache/airflow/pull/31830#issuecomment-1891071716
> @potiuk i think the current PR generates adds the todos to the docs PR -- not the Vote message -- can you double check? from my reading of your message, it's seems that is where you want it too? Nope. It adds the TODOs at the moment where "issue generation" happens. Issue generation happens when the Release candidates are already in SVN and they are about to be announced. This is https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md#prepare-issue-in-github-to-keep-status-of-testing The process looks like follows: 1) RM generates PR with CHANGELOG and version bump for all providers that had merged changes since their last release 2) This PR can be rebased and updated as the RM makes a "last call" - hey are there any PRs that should be merged 3) Once this PR is rebased one last time it gets merged (after checking that no new changes were merged) 4) At this poing RM creates an RC tag and builds packages (from the merged changelog commit) 5) The next step is that RM creates an issue that summarizes all the issues/prs/changes and ask people to test it 6) Then RM sends VOTE email with link to that issue 7) After few days when things get approved, all providers that were not `-1`-ed are relased from that commit from point 3) 8) All the `-1`-ed providers are moved to next wave (which might be accelerated - only the `-1`ed providers with bugfixes, or regular one - where all providers that got changes after 3) are included -> this is something I added recently So what you added is happening at point 5) -> TODOS generated here are far to late to do anything about it, because the issue is about TESTING already released RCs What I **think** your change could do is to have a NEW issue (fix those deprecations) happening either after 1) or even before 1) is even attempted. -- 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]
