Hello,
Apache Airflow 2.8.1 (based on RC1) has been accepted.
7 "+1" binding votes received:
- Ephraim Anierobi
- Jarek Potiuk
- Jed Cunningham
- Hussein Awala
- Bolke de Bruin
- Elad Kalif
- Andrey Anshin
5 "+1" non-binding votes received:
- Amogh Desai
- Phani Kumar
- Rom Sharon
- Rahul Vats
+1 (non-binding)
Best regards,
*Pankaj Koti*
Senior Software Engineer (Airflow OSS Engineering team)
Location: Pune, Maharashtra, India
Timezone: Indian Standard Time (IST)
Phone: +91 9730079985
On Fri, Jan 19, 2024 at 12:00 PM Ephraim Anierobi
wrote:
> Hi Bolke,
>
> I have included the link
Hi Bolke,
I have included the link to what will be in the next release, in the email
template as you suggested through this PR
https://github.com/apache/airflow/pull/36863.
Thanks for the suggestion!
- Ephraim
On Fri, 19 Jan 2024 at 05:35, Rahul Vats wrote:
> +1 (non-binding).
>
>-
+1 (non-binding).
- Verified that running our example DAGs did not reveal any regressions.
- Verified installation with helm chart and running example DAGS.
- Verified the API endpoints and no regressions were found.
Regards,
Rahul Vats
9953794332
On Fri, 19 Jan 2024 at 00:46, Andrey
+1 binding
Checked signatures, files, licences and also my changes
One small nit which I've noticed when executing check_files.py. After we
switch to hatch the source distribution name include non-normalized name:
use _ (underscore) instead of - (hyphen): apache_airflow-2.8.1.tar.gz
instead of
Well that's the whole point about repeating "SemVer" enough times should be
enough to distinct the feature (2.9.0) release from patchlevel (BTW.
patchlevel name comes from SemVer so I am not sure if that changes much to
mention it).
But maybe another suggestion - I think maybe you can propose a PR
+1 Non binding
בתאריך יום ה׳, 18 בינו׳ 2024 ב-13:31 מאת Elad Kalif <elad...@apache.org
>:
> +1 binding
>
> On Thu, Jan 18, 2024 at 12:52 PM Bolke de Bruin wrote:
>
> > +1 binding.
> >
> > On Thu, 18 Jan 2024 at 11:00, Hussein Awala wrote:
> >
> > > +1 (binding) Checked signatures,
+1 binding
On Thu, Jan 18, 2024 at 12:52 PM Bolke de Bruin wrote:
> +1 binding.
>
> On Thu, 18 Jan 2024 at 11:00, Hussein Awala wrote:
>
> > +1 (binding) Checked signatures, checksums, licences and sources, I also
> > ran some testing DAGs; all look good.
> >
> >
> > On Thu 18 Jan 2024 at
Thanks Jarek, as mentioned in the other thread it seemed to break a
different pattern for me. I was aware of "what goes into the next release",
but the title seemed more indicative of roadmap items and thus geared to
consumers of a release.
Earlier, it seems, I was helped by others when PRs were
+1 binding.
On Thu, 18 Jan 2024 at 11:00, Hussein Awala wrote:
> +1 (binding) Checked signatures, checksums, licences and sources, I also
> ran some testing DAGs; all look good.
>
>
> On Thu 18 Jan 2024 at 06:54, Phani Kumar .invalid>
> wrote:
>
> > +1 non binding
> >
> > On Thu, Jan 18, 2024
Thanks Ephraim, that pattern did not catch my attention (or I thought it
was breaking a different pattern). Maybe it is nice to label the release
(patch, major - yes I know it is semver but still) and include the link in
the voting template? That makes it easier for the more occasional view.
B.
+1 (binding) Checked signatures, checksums, licences and sources, I also
ran some testing DAGs; all look good.
On Thu 18 Jan 2024 at 06:54, Phani Kumar
wrote:
> +1 non binding
>
> On Thu, Jan 18, 2024 at 10:30 AM Amogh Desai
> wrote:
>
> > +1 non binding
> >
> > Installed the RC with helm
Great idea. I will take a look at this shortly.
Thanks!
On Thu, 18 Jan 2024 at 1:48 PM, Jarek Potiuk wrote:
> Created PR https://github.com/apache/airflow/pull/36858 where I proposed
> a separate document - with a bit more polished version of what I wrote
> above, interlinked with the succinct
Created PR https://github.com/apache/airflow/pull/36858 where I proposed a
separate document - with a bit more polished version of what I wrote above,
interlinked with the succinct README chapter we already have.
I also expanded there a bit "What's the purpose of patch-level release"
explaining
I think if anything - that should be a separate page in our GitHub -
which will be a) easier to do b) maybe indeed makes sense c) this is where
we put "developer" docs.
I think we agreed already quite some time ago that "airflow.apache.org" is
generally for the users and all the docs for
+1 non binding
On Thu, Jan 18, 2024 at 10:30 AM Amogh Desai
wrote:
> +1 non binding
>
> Installed the RC with helm charts, tried a couple of installation
> configurations
> and ran a few examples, not seeing any regression.
>
> Thanks & Regards,
> Amogh Desai
>
> On Thu, Jan 18, 2024 at 12:16
+1 non binding
Installed the RC with helm charts, tried a couple of installation
configurations
and ran a few examples, not seeing any regression.
Thanks & Regards,
Amogh Desai
On Thu, Jan 18, 2024 at 12:16 AM Jed Cunningham
wrote:
> +1 (binding)
>
> Checked signatures, checksums, licences.
Thanks @Jarek Potiuk !
I vaguely knew the process but not in such detail, thanks for putting it
together in this email.
I will visit the document
https://github.com/apache/airflow?tab=readme-ov-file#what-goes-into-the-next-release
and if I find any clarifications, I will send it across as a PR.
+1 (binding)
Checked signatures, checksums, licences. Used it with the helm chart with a
few different configs
Hi Bolke,
Thanks for checking up on this release.
The changes in Airflow.io are mostly improvement changes and this is a
patch release. In patch releases, we don't include improvement changes and
new features. We only include bug fixes, doc changes, and miscellaneous
changes that are not core to
I separate it out, because it seems that despite the efforts to explain and
document how our releases work It's not clear even for the PMC chair, so
likely it warrants a separate thread - also it will be easier to find it in
the archives this way.
I think this is an important topic that all
Just checking:
I see that some improvements to Airflow.io (two weeks ago) were not included
and some provider updates neither. Haven't checked anything else yet.
Is that intentional? Ie. is that the purpose of this release. Other big(ger)
and more recent changes have been included hence
+1 (binding): Checked all my changes, I ran airflow in a few combinations
(MySQL / Postgres Local/Celery executor. It looks and works well - run a
few dags and navigated through a number of screens. Checked licences,
signatures, checksums, performed a "reproducible build" check and it worked
(with
Hey fellow Airflowers,
I have cut Airflow 2.8.1rc1. This email is calling a vote on the release,
which will last at least 72 hours, from Tuesday, January 16, 2024 at 10:30
am UTC
until Friday, January 19, 2024, at 10:30 am UTC
24 matches
Mail list logo
