Suggestion: just to aid that work - Kaxil - Maybe we should go back to the
previous way (before cherry-picker) of marking things as ready to be
cherry-picked - Marking them as "Airflow 3.0.0" milestones - this way we
will make sure that some important things will not be lost ?
I think we still ha
Yeah, I removed that label, too, to avoid any confusion. Once 3.0.0 is
officially released, we’ll return to `backport-to-v3-0-test` for automatic
backport -- where the PR author or a committer could do that -- but we can
discuss than once we reach there.
I think we just need to clarify who and wh
Just one comment - following our discussion.. I perfectly understand we
want to take more control now on what is merged. And if you want to take
responsibility there then I am fine ( but also do not envy you :)
I think we just need to clarify who and when should add the backport-to
labels PRS (i
Hey everyone,
As we approach the final stages of the Airflow 3.0.0 release, the main
branch is now officially targeting Airflow 3.1.
*What this means*:
• PR authors and contributors should continue working as usual -- nothing
changes in how PRs are submitted or merged.
• However, starting now, al
