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/09/09 23:11:57 UTC
Airflow 3.1.0 Release Branch Created - Cherry-pick Process & Guidelines
Dear Airflow Community,
Following the announcement of Airflow 3.1.0b1, I want to inform you that
the **v3-1-test** branch is now our official release branch for Airflow
3.1.0.
*Effective immediately*:
- **v3-1-test** is the release branch for all 3.1.0 releases (beta, RC, and
final)
- I will be manually cherry-picking changes from main to v3-1-test on a *daily
basis* through RC1 (expected end of next week)
- **No new features will be cherry-picked** - only critical bug fixes,
feature completion changes and release preparation changes
*Important: Do NOT Cherry-pick Directly*
**Please do not cherry-pick any changes to v3-1-test directly**, even if
you have permissions to do so.
Here's why this process is critical:
1. **Quality Control**: Each change needs to be vetted for release stability
2. **Release Notes**: All changes must be properly documented in release
notes
3. **Test Stability**: We need to prevent the test surface from constantly
shifting
*How to Get Changes Into 3.1.0*
If you have a change that should be included in 3.1.0:
1. *Merge to main first* - ensure it passes all CI checks
2. *Add to 3.1.0 milestone* -
https://github.com/apache/airflow/milestone/112
*What Qualifies for Cherry-picking*
**Will be considered:**
- Critical bug fixes affecting core functionality
- Translation updates (if significant)
- Feature completion changes for 3.1
- Security fixes
- Blocker issues preventing testing
- Documentation corrections for new 3.1.0 features
I'll soon create PR(s) to make main branch target to Airflow 3.2
Thank you for your cooperation in maintaining release quality and
stability. This disciplined approach helps ensure we deliver a robust 3.1.0
release while keeping the development momentum going for future versions.
Questions about the release process? Feel free to reach out on the dev
mailing list or tag me directly.
Thanks,
Kaxil
Re: Airflow 3.1.0 Release Branch Created - Cherry-pick Process & Guidelines
Posted by Amogh Desai <am...@apache.org>.
Thanks for sharing Kaxil. Good to have this information!
Thanks & Regards,
Amogh Desai
On Wed, Sep 10, 2025 at 6:03 AM Jarek Potiuk <ja...@potiuk.com> wrote:
> Super helpful ! Thanks Kaxil.
>
>
> Greetings from Minneapolis
>
> wt., 9 wrz 2025, 18:13 użytkownik Kaxil Naik <ka...@gmail.com>
> napisał:
>
> > Dear Airflow Community,
> >
> > Following the announcement of Airflow 3.1.0b1, I want to inform you that
> > the **v3-1-test** branch is now our official release branch for Airflow
> > 3.1.0.
> >
> > *Effective immediately*:
> >
> > - **v3-1-test** is the release branch for all 3.1.0 releases (beta, RC,
> and
> > final)
> > - I will be manually cherry-picking changes from main to v3-1-test on a
> > *daily
> > basis* through RC1 (expected end of next week)
> > - **No new features will be cherry-picked** - only critical bug fixes,
> > feature completion changes and release preparation changes
> >
> > *Important: Do NOT Cherry-pick Directly*
> >
> > **Please do not cherry-pick any changes to v3-1-test directly**, even if
> > you have permissions to do so.
> >
> > Here's why this process is critical:
> >
> > 1. **Quality Control**: Each change needs to be vetted for release
> > stability
> > 2. **Release Notes**: All changes must be properly documented in release
> > notes
> > 3. **Test Stability**: We need to prevent the test surface from
> constantly
> > shifting
> >
> > *How to Get Changes Into 3.1.0*
> >
> > If you have a change that should be included in 3.1.0:
> >
> > 1. *Merge to main first* - ensure it passes all CI checks
> > 2. *Add to 3.1.0 milestone* -
> > https://github.com/apache/airflow/milestone/112
> >
> > *What Qualifies for Cherry-picking*
> >
> > **Will be considered:**
> > - Critical bug fixes affecting core functionality
> > - Translation updates (if significant)
> > - Feature completion changes for 3.1
> > - Security fixes
> > - Blocker issues preventing testing
> > - Documentation corrections for new 3.1.0 features
> >
> > I'll soon create PR(s) to make main branch target to Airflow 3.2
> >
> > Thank you for your cooperation in maintaining release quality and
> > stability. This disciplined approach helps ensure we deliver a robust
> 3.1.0
> > release while keeping the development momentum going for future versions.
> >
> > Questions about the release process? Feel free to reach out on the dev
> > mailing list or tag me directly.
> >
> > Thanks,
> > Kaxil
> >
>
Re: Airflow 3.1.0 Release Branch Created - Cherry-pick Process & Guidelines
Posted by Jarek Potiuk <ja...@potiuk.com>.
Super helpful ! Thanks Kaxil.
Greetings from Minneapolis
wt., 9 wrz 2025, 18:13 użytkownik Kaxil Naik <ka...@gmail.com> napisał:
> Dear Airflow Community,
>
> Following the announcement of Airflow 3.1.0b1, I want to inform you that
> the **v3-1-test** branch is now our official release branch for Airflow
> 3.1.0.
>
> *Effective immediately*:
>
> - **v3-1-test** is the release branch for all 3.1.0 releases (beta, RC, and
> final)
> - I will be manually cherry-picking changes from main to v3-1-test on a
> *daily
> basis* through RC1 (expected end of next week)
> - **No new features will be cherry-picked** - only critical bug fixes,
> feature completion changes and release preparation changes
>
> *Important: Do NOT Cherry-pick Directly*
>
> **Please do not cherry-pick any changes to v3-1-test directly**, even if
> you have permissions to do so.
>
> Here's why this process is critical:
>
> 1. **Quality Control**: Each change needs to be vetted for release
> stability
> 2. **Release Notes**: All changes must be properly documented in release
> notes
> 3. **Test Stability**: We need to prevent the test surface from constantly
> shifting
>
> *How to Get Changes Into 3.1.0*
>
> If you have a change that should be included in 3.1.0:
>
> 1. *Merge to main first* - ensure it passes all CI checks
> 2. *Add to 3.1.0 milestone* -
> https://github.com/apache/airflow/milestone/112
>
> *What Qualifies for Cherry-picking*
>
> **Will be considered:**
> - Critical bug fixes affecting core functionality
> - Translation updates (if significant)
> - Feature completion changes for 3.1
> - Security fixes
> - Blocker issues preventing testing
> - Documentation corrections for new 3.1.0 features
>
> I'll soon create PR(s) to make main branch target to Airflow 3.2
>
> Thank you for your cooperation in maintaining release quality and
> stability. This disciplined approach helps ensure we deliver a robust 3.1.0
> release while keeping the development momentum going for future versions.
>
> Questions about the release process? Feel free to reach out on the dev
> mailing list or tag me directly.
>
> Thanks,
> Kaxil
>