Now that Airflow 3.0.0 is officially released, I have re-enabled the `backport-to-v3-0-test` label. If you (Reviews/Committers) want to guarantee that a PR is included in the next patch release, use `backport-to-v3-0-test` label on that PR before merging. This should work if there are no conflicts.
On Thu, 17 Apr 2025 at 19:13, Kaxil Naik <kaxiln...@gmail.com> wrote: > Hey team, > > We now have milestones for 3.0.1, 3.1.0 and 3.1+. > > https://github.com/apache/airflow/milestone/111 > https://github.com/apache/airflow/milestone/112 > https://github.com/apache/airflow/milestone/106 > > Please add PRs & Issues with respective milestones to set expectations > with the release manager and end users. > > We will soon enable the backport label after 3.0.0 release, so PRs can be > automatically cherry-picked when there are no conflicts. > > Regards, > Kaxil > > > > >
