You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Kaxil Naik <ka...@gmail.com> on 2025/04/17 13:43:38 UTC
Marking issues & PRs for Airflow >3.0.0
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
Re: Marking issues & PRs for Airflow >3.0.0
Posted by Pavankumar Gopidesu <go...@gmail.com>.
Yeah cool.
Another thing I would like to mention. when PR cherry-picked using label
backport-to-*. The default PR state is DRAFT on a backported branch. so
please set it back to Read For Review. with this way the workflows will get
triggered.
Pavan
On Thu, Apr 24, 2025 at 11:42 AM Amogh Desai <am...@gmail.com>
wrote:
> Great thanks for the update Kaxil!
>
> It definitely is helpful.
>
> Thanks & Regards,
> Amogh Desai
>
>
> On Thu, Apr 24, 2025 at 3:47 PM Jarek Potiuk <ja...@potiuk.com> wrote:
>
> > Cool. I would also suggest and encourage those who merge fixes to do so.
> >
> > If we all do the backporting with the label (before merging) or Github
> > workflow/ cherry-picker tool (after) it makes it easier to keep
> `v3-0-test`
> > branch "green" - there are some external factors that influence the
> > "greenness" of it, and it makes life easier for those people who are
> > involved in releasing - so exercising empathy towards Kaxil, myself and
> > other people involved in making the release works is simply a good idea.
> >
> > I was initially sceptical about cherry-picker workflow, but after using
> it,
> > I think it has this nice feature of sharing the burden of preparing the
> > release rather than accumulating the stress on a single person or a few
> > people.
> >
> > I added https://github.com/apache/airflow/pull/49701 to update our
> > README_AIRFLOW3_DEV.md to make it easy to follow (we had only airflow
> 3->
> > 2 instructions but now we should have similar main -> 3.0.*.
> >
> > J.
> >
> >
> > On Thu, Apr 24, 2025 at 11:11 AM Kaxil Naik <ka...@gmail.com> wrote:
> >
> > > From time to time, I will be cherry-picking things from GitHub
> milestones
> > > too to v3-0-test too to reduce the workload near the release date.
> > >
> > > On Thu, 24 Apr 2025 at 14:39, Kaxil Naik <ka...@gmail.com> wrote:
> > >
> > > > 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 <ka...@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
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > >
> >
>
Re: Marking issues & PRs for Airflow >3.0.0
Posted by Amogh Desai <am...@gmail.com>.
Great thanks for the update Kaxil!
It definitely is helpful.
Thanks & Regards,
Amogh Desai
On Thu, Apr 24, 2025 at 3:47 PM Jarek Potiuk <ja...@potiuk.com> wrote:
> Cool. I would also suggest and encourage those who merge fixes to do so.
>
> If we all do the backporting with the label (before merging) or Github
> workflow/ cherry-picker tool (after) it makes it easier to keep `v3-0-test`
> branch "green" - there are some external factors that influence the
> "greenness" of it, and it makes life easier for those people who are
> involved in releasing - so exercising empathy towards Kaxil, myself and
> other people involved in making the release works is simply a good idea.
>
> I was initially sceptical about cherry-picker workflow, but after using it,
> I think it has this nice feature of sharing the burden of preparing the
> release rather than accumulating the stress on a single person or a few
> people.
>
> I added https://github.com/apache/airflow/pull/49701 to update our
> README_AIRFLOW3_DEV.md to make it easy to follow (we had only airflow 3->
> 2 instructions but now we should have similar main -> 3.0.*.
>
> J.
>
>
> On Thu, Apr 24, 2025 at 11:11 AM Kaxil Naik <ka...@gmail.com> wrote:
>
> > From time to time, I will be cherry-picking things from GitHub milestones
> > too to v3-0-test too to reduce the workload near the release date.
> >
> > On Thu, 24 Apr 2025 at 14:39, Kaxil Naik <ka...@gmail.com> wrote:
> >
> > > 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 <ka...@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
> > >>
> > >>
> > >>
> > >>
> > >>
> >
>
Re: Marking issues & PRs for Airflow >3.0.0
Posted by Jarek Potiuk <ja...@potiuk.com>.
Cool. I would also suggest and encourage those who merge fixes to do so.
If we all do the backporting with the label (before merging) or Github
workflow/ cherry-picker tool (after) it makes it easier to keep `v3-0-test`
branch "green" - there are some external factors that influence the
"greenness" of it, and it makes life easier for those people who are
involved in releasing - so exercising empathy towards Kaxil, myself and
other people involved in making the release works is simply a good idea.
I was initially sceptical about cherry-picker workflow, but after using it,
I think it has this nice feature of sharing the burden of preparing the
release rather than accumulating the stress on a single person or a few
people.
I added https://github.com/apache/airflow/pull/49701 to update our
README_AIRFLOW3_DEV.md to make it easy to follow (we had only airflow 3->
2 instructions but now we should have similar main -> 3.0.*.
J.
On Thu, Apr 24, 2025 at 11:11 AM Kaxil Naik <ka...@gmail.com> wrote:
> From time to time, I will be cherry-picking things from GitHub milestones
> too to v3-0-test too to reduce the workload near the release date.
>
> On Thu, 24 Apr 2025 at 14:39, Kaxil Naik <ka...@gmail.com> wrote:
>
> > 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 <ka...@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
> >>
> >>
> >>
> >>
> >>
>
Re: Marking issues & PRs for Airflow >3.0.0
Posted by Kaxil Naik <ka...@gmail.com>.
From time to time, I will be cherry-picking things from GitHub milestones
too to v3-0-test too to reduce the workload near the release date.
On Thu, 24 Apr 2025 at 14:39, Kaxil Naik <ka...@gmail.com> wrote:
> 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 <ka...@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
>>
>>
>>
>>
>>
Re: Marking issues & PRs for Airflow >3.0.0
Posted by Kaxil Naik <ka...@gmail.com>.
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 <ka...@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
>
>
>
>
>