Re: [VOTE] Release Airflow 2.5.0 from 2.5.0rc1

Makes sense, thank you for explaining Ephraim and Ash :) Le sam. 26 nov. 2022 à 13:12, Ash Berlin-Taylor a écrit : > For minor releases there are too many changes, so we just use the thread. > (Compare with patch releases where there should only be bug fixes to check) > > -a > > On 26 November

Re: [DISCUSS] Allow shorter voting periods for subsequent RCs

I agree that having to wait another 72 hours can be a little annoying. I like Jarek idea of an incompressible 24h window if the previous RC was close to an end. This feels like a good compromise and also leave people some time to do further testing in case the highlighted bug is tied to other issu

Re: [ANNOUNCE] New committer Andrey Anshin (Taragolis)

Well deserved indeed! Congratulations Andrey :) Pierre Le ven. 2 déc. 2022 à 16:16, Beck, Vincent a écrit : > Congrats! Well deserved! > > On 2022-12-02, 2:31 AM, "Jarek Potiuk" wrote: > > CAUTION: This email originated from outside of the organization. Do > not click links or open attach

Re: [DISCUSSION] Release of API clients

Hello guys, Just a heads up on this one. To summarize what we seem to agree on: - for each minor/major release of airflow, we should systematically release new versions of api clients accordingly (python/go clients). - we can patch clients independently to fix specific issues (documentation, gene

[LAZY CONSENSUS] Release of API Clients

Hi all, *Context:* Dag author should be able to use API clients to communicate with airflow for everything that is not internal and covered by future AIP-44. The goal of this proposal is to update the release process of our API clients so they are compatible and up to date with the latest airflow

Re: [LAZY CONSENSUS] Release of API Clients

Hello all, 72h hours have passed without opposition, therefore the proposal is accepted and we can start working on it :) Thanks you, Pierre Le lun. 5 déc. 2022 à 18:44, Pierre Jeambrun a écrit : > Hi all, > > *Context:* > Dag author should be able to use API clients to comm

Re: [VOTE] New Provider: Cloudera

Hello, I am really excited about a public official cloudera provider for airflow. This would be a great addition to the airflow ecosystem. System tests would be an additional layer that would be great for the CI and release process, but would individual contributors be able to run these system te

Re: [VOTE] New Provider: Cloudera

anization is not expected to release outside the Apache process, who is? > Maybe I'm misunderstanding, but I thought that the idea was that providers > going forward would be mostly third party which allows for a larger and > more vibrant ecosystem. > > Collin McNulty > > On

Re: [LAZY CONSENSUS] Release of API Clients

t; aware of the policy ? (also I guess better to be written in the release >> docs procedure) >> >> On Thu, Dec 8, 2022 at 7:50 PM Pierre Jeambrun >> wrote: >> >>> Hello all, >>> >>> 72h hours have passed without opposition, therefore the pr

Re: [ANNOUNCE] New committer Niko Oliveira (o-nikolas)

Congratulations Niko! Pierre On Tue 20 Dec 2022 at 00:21, Ping Zhang wrote: > Congrats Niko 👍 > > Thanks, > > Ping > > > On Mon, Dec 19, 2022 at 3:18 PM Xiaodong Deng wrote: > >> Congrats! >> >> >> >> On Mon, Dec 19, 2022 at 13:41 Felix Uellendall >> wrote: >> >>> Congrats! >>> >>> >>> >>> Se

Re: [DISCUSS] AIP-52 Automatic setup and tear down tasks

Hello Ash, I also love this. The AIP answered the question I had. Best, Pierre Le mar. 20 déc. 2022 à 04:41, Ping Zhang a écrit : > Hi Ash, > > I love this idea, especially about the `teardown`, which is way cleaner > than defining a task as the downstream task of all other tasks with > trigge

Re: [LAZY CONSENSUS] Release of API Clients

Hello all, Here is the PR documenting our policy: https://github.com/apache/airflow/pull/28521 Best regards, Pierre Le jeu. 15 déc. 2022 à 01:40, Pierre Jeambrun a écrit : > Very good idea, thanks for the pointers. I will open a PR this week > to update our doc :) > > Best regards

Re: [VOTE] AIP-50 Trigger DAG UI Extension with Flexible User Form Concept

+1 binding On Sat 24 Dec 2022 at 12:09, Xinbin Huang wrote: > > +1 binding > > On Fri, Dec 23, 2022 at 5:43 PM Kaxil Naik wrote: > >> +1 binding >> >> On Fri, 23 Dec 2022 at 16:09, Constance Martineau >> wrote: >> >>> I somehow missed the discussion for this earlier. I can't comment on >>> imp

Re: [VOTE] AIP-52 Automatic setup and teardown tasks

+1 (binding) Le lun. 9 janv. 2023 à 21:12, Vikram Koka a écrit : > +1 binding > > Vikram > > > On Mon, Jan 9, 2023 at 11:23 AM Ping Zhang wrote: > >> +1 binding >> >> Thanks, >> >> Ping >> >> >> On Mon, Jan 9, 2023 at 11:22 AM Ephraim Anierobi < >> ephraimanier...@gmail.com> wrote: >> >>> +1 bi

[VOTE] Release Airflow 2.5.1 from 2.5.1rc1

(#28517) - Remove outdated Optional Provider Feature outdated documentation (#28506) - Add documentation for [core] mp_start_method config (#27993) - Documentation for the LocalTaskJob return code counter (#27972) - Note which versions of Python are supported (#27798) Cheers, Pierre Jeambrun

Re: [VOTE] Release Airflow 2.5.1 from 2.5.1rc1

A bug was found in rc1 that will necessitate an rc2. I'm canceling this vote and will create 2.5.0rc2 soon. Best regards, Pierre Jeambrun Le lun. 16 janv. 2023 à 19:56, Jarek Potiuk a écrit : > +1 (binding) . Tested (almost) all changes I've been involved in, checked > sou

Re: [VOTE] Release Airflow 2.5.1 from 2.5.1rc1

Correcting myself, 2.5.1rc2 Le mar. 17 janv. 2023 à 19:04, Pierre Jeambrun a écrit : > A bug was found in rc1 that will necessitate an rc2. I'm canceling this > vote and will create 2.5.0rc2 soon. > > Best regards, > Pierre Jeambrun > > Le lun. 16 janv. 2023 à 19

[VOTE] Release Airflow 2.5.1 from 2.5.1rc2

Hey fellow Airflowers, I have cut Airflow 2.5.1rc2. This email is calling a vote on the release, which will last *24 hours*, from Wednesday, January 18, 2023 at 22:00 pm UTC until Thursday, January 19, 2023 at 22:00 pm UTC, and until 3 binding +1 votes have been received. https://www.timeanddate.

[RESULT][VOTE] Release Airflow 2.5.1 from 2.5.1rc2

Hello, Apache Airflow 2.5.1 (based on RC2) has been accepted. 4 "+1" binding votes received: - Jarek Potiuk - Ephraim Anierobi - Jed Cunningham - Kaxil Naik 4 "+1" non-binding votes received: - Pankaj Singh - Josh Fell - Dennis Akpenyi - Pierre Jeambrun Vote thread: http

Re: [VOTE] Release Airflow Python Client 2.5.0 based on 2.5.0rc1

+1 (non-binding) Le lun. 16 janv. 2023 à 13:23, Ephraim Anierobi a écrit : > Hello everyone, > > I have cut the first release candidate for the Airflow Python Client 2.5.0. > The client consists of APIs corresponding to REST APIs available in > *Apache Airflow 2.5.1* release candidate. This emai

[ANNOUNCE] Apache Airflow 2.5.1 Released

lease notes here for more details: https://airflow.apache.org/docs/apache-airflow/2.5.1/release_notes.html Container images are published at: https://hub.docker.com/r/apache/airflow/tags/?page=1&name=2.5.1 Cheers, Pierre Jeambrun

Re: Amazon provider package system tests dashboard

This is really cool, thanks for setting all of this up! I just took a look at the dashboard and it is really helpful :) Le lun. 23 janv. 2023 à 16:55, Beck, Vincent a écrit : > The AWS Airflow team is happy to announce that the dashboard we have been > building which summarizes the health statu

Re: [DISCUSSION] Assessing what is a breaking change for Airflow (SemVer context)

Strong +1 for the BaseExecutor. This relates to a discussion we had with Niko about AIP-51 where we talked about having at some point all our Executors to extend this common base class. At the moment, most of our mixed executors do not. As a consequence we had a few surprises while implementing A

[VOTE] Release Airflow Python Client 2.5.1 from 2.5.1rc1

Hey fellow Airflowers, I have cut the first release candidate for the Airflow Python Client 2.5.1rc1. The client consists of APIs corresponding to REST APIs available in *Apache Airflow 2.5.0*. This email is calling for a vote on the release, which will last for 72 hours. Consider this my (non-bi

[VOTE] Release Airflow Go Client 2.5.0 from 2.5.0rc1

Hey fellow Airflowers, I have cut the first release candidate for the Airflow Go Client 2.5.0rc1. The client consists of APIs corresponding to REST APIs available in *Apache Airflow 2.5.0*. This email is calling for a vote on the release, which will last for 72 hours. Consider this my (non-bindin

Re: [VOTE] PR of the Month

Hello, I vote for #27063 :) Le lun. 30 janv. 2023 à 20:17, John Thomas a écrit : > It's a new year and a new newsletter! This vote is a bit late because I > had to do some work on the script, but as usual it closes at 9a MST on > Wednesday, Feb 1. > > The script has highlighted the following, b

Re: [VOTE] Release Airflow Python Client 2.5.1 from 2.5.1rc1

Hello all, We need more votes here :) I would really like to see this move forward as it fixes an important authentication issue introduced in the previous release. (2.5.0) Best regards, Pierre

[RESULT][VOTE] Release Airflow Python Client 2.5.1 from 2.5.1rc1

Hello, Apache Airflow Python Client 2.5.1 (based on RC1) has been accepted. 3 "+1" binding votes received: - Jed Cunningham - Ephraim Anierobi - Elad Kalif 1 "+1" non-binding votes received: - Pierre Jeambrun Vote thread: https://lists.apache.org/thread/jn7w5ry2z67r9sq67t

[ANNOUNCE] Apache Airflow Python Client version 2.5.1 Released

https://github.com/apache/airflow-client-python/blob/master/CHANGELOG.md Cheers, Pierre Jeambrun

Re: Another Milestone for Airflow & the community

This is a very exciting news! On Thu 2 Feb 2023 at 06:31, Ping Zhang wrote: > Wow, that is great news! Thanks for sharing. > > Thanks, > > Ping > > > On Wed, Feb 1, 2023 at 5:51 PM Kaxil Naik wrote: > >> Source: >> >> https://techcommunity.microsoft.com/t5/azure-data-factory-blog/introducing-ma

[RESULT][VOTE] Release Airflow Go Client 2.5.0 from 2.5.0rc1

Hello, Apache Airflow Go Client 2.5.0 (based on RC1) has been accepted. 3 "+1" binding votes received: - Jed Cunningham - Ephraim Anierobi - Jarek Potiuk 1 "+1" non-binding votes received: - Pierre Jeambrun Vote thread: https://lists.apache.org/thread/d56pyyx8m15so735nm

[ANNOUNCE] Apache Airflow Go Client version 2.5.0 Released

rflow/README.md Find the CHANGELOG here for more details: https://github.com/apache/airflow-client-go/blob/main/CHANGELOG.md Cheers, Pierre Jeambrun

Re: [NOTICE] Upcoming global changes to default GitHub Actions behavior for outside collaborators

Hello, I share Jarek and Dennis' concerns. It would be very hard to maintain enough responsiveness to not discourage external contributions while still trying to actually check the changes before approving a workflow. We have hundreds of workflows a day (~150 - 200 in the last 24hours, it would

Re: [VOTE] Move K8S / Celery (and related) executors to respective providers

+1 (binding) On Wed 22 Feb 2023 at 15:37, Kaxil Naik wrote: > +1 binding > > On Wed, 22 Feb 2023 at 07:41, Ping Zhang wrote: > >> +1 binding >> >> On Mon, Feb 20, 2023 at 23:46 Jarek Potiuk wrote: >> >>> Hello everyone, >>> >>> This is a call for the vote to make an internal change to move the

Re: [VOTE] February PR of the Month

+1 to #27758, this is really cool! Le ven. 24 févr. 2023 à 23:55, Jed Cunningham a écrit : > +1 to #27758 >

Re: [DISCUSS] Allow shorter voting periods for subsequent RCs

Hello, I don’t think we had a lazy consensus on this matter but we already applied it a couple of times before (for 2.5.1 and another one before that, if I am not mistaken). I think it would be good to start a lazy consensus, just to follow the standard protocol and have a record of this in our a

Re: [DISCUSS] Allow shorter voting periods for subsequent RCs

I will start the lazy consensus tonight :) On Tue 7 Mar 2023 at 18:02, Kaxil Naik wrote: > +1 > > On Tue, 7 Mar 2023 at 16:56, Jarek Potiuk wrote: > > > +1 > > > > On Tue, Mar 7, 2023 at 1:11 PM Pierre Jeambrun > > wrote: > > > > > > Hello

[LAZY CONSENSUS] Allow shorter voting periods for subsequent RCs

Hi all, *Context:*Having a 72h vote window on each subsequent RCs can slow down the release process, bring some annoyance and add load on the release manager. This could be avoided, especially when the new RC only ships a few extra commits. This proposal would bring some flexibility to the voting

Re: [LAZY CONSENSUS] Allow shorter voting periods for subsequent RCs

72 hours have passed, we will start using this policy for our future releases. Thanks Le mar. 7 mars 2023 à 21:29, Ferruzzi, Dennis a écrit : > +1 (non-bindingly lazy) > > > ____ > From: Pierre Jeambrun > Sent: Tuesday, March 7, 2023

[VOTE] Release Airflow 2.5.2 from 2.5.2rc1

Hey fellow Airflowers, I have cut Airflow 2.5.2rc1. This email is calling a vote on the release, which will last at least 72 hours, from Friday, March 10, 2023 at 9:00 pm UTC until Monday, October 13, 2023 at 9:00 pm UTC, and until 3 binding +1 votes have been received. Status of testing of the r

Re: [VOTE] Release Airflow 2.5.2 from 2.5.2rc1

Correcting myself to avoid any confusion, vote end date is Monday, March 13, 2023 at 9:00 pm UTC (not October) Le sam. 11 mars 2023 à 19:47, Jed Cunningham a écrit : > +1 (binding) > > Checked signatures, checksums, licences. Used it with the helm chart with a > few different configs. >

Re: [VOTE] Release Airflow 2.5.2 from 2.5.2rc1

A bug was found in rc1 that will necessitate an rc2. I'm canceling this vote and we will create 2.5.2rc2 soon. Best regards, Pierre Jeambrun Le lun. 13 mars 2023 à 15:17, Brent Bovenzi a écrit : > +1 binding > > On Mon, Mar 13, 2023 at 3:56 AM Phani Kumar > wrote: >

[VOTE] Release Airflow 2.5.2 from 2.5.2rc2

Hey fellow Airflowers, I have cut Airflow 2.5.2rc2. This email is calling a vote on the release, which will last *24 hours*, from Monday, March 13, 2023 at 9:45 pm UTC until Tuesday, March 14, 2023 at 9:45 pm UTC, and until 3 binding +1 votes have been received. Status of testing of the release i

Re: [VOTE] Release Airflow 2.5.2 from 2.5.2rc2

ce 2.5.2rc1" since we already voted on rc1 rather > than full changelog > > On Mon, 13 Mar 2023 at 21:46, Pierre Jeambrun > wrote: > > > Hey fellow Airflowers, > > > > I have cut Airflow 2.5.2rc2. This email is calling a vote on the release, > > which will

[RESULT][VOTE] Release Airflow 2.5.2 from 2.5.2rc2

Hello, Apache Airflow 2.5.2 (based on RC2) has been accepted. 5 "+1" binding votes received: - Jed Cunningham - Kaxil Naik - Jarek Potiuk - Ephraim Anierobi - Elad Kalif 5 "+1" non-binding votes received: - Josh Fell - Hussein Awala - Pankaj Singh - Phani Kumar - Pierre J

[ANNOUNCE] Apache Airflow 2.5.2 Released

lease notes here for more details: https://airflow.apache.org/docs/apache-airflow/2.5.2/release_notes.html Container images are published at: https://hub.docker.com/r/apache/airflow/tags/?page=1&name=2.5.2 Cheers, Pierre Jeambrun

Re: [ANNOUNCE] New PMC member: Brent Bovenzi

Congratulations Brent, well deserved :) Le mer. 15 mars 2023 à 18:55, Oliveira, Niko a écrit : > Congrats Brent!! > > > From: Jorrick Sleijster > Sent: Wednesday, March 15, 2023 9:09:07 AM > To: dev@airflow.apache.org > Subject: RE: [EXTERNAL][ANNOUNCE] New PMC

Re: [ANNOUNCE] New PMC member: Pierre Jeambrun

March 15, 2023 2:47:31 AM > To: dev@airflow.apache.org > Subject: RE: [EXTERNAL][ANNOUNCE] New PMC member: Pierre Jeambrun > > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unless you can confirm the sender

Re: [AIP-49 OTel] [Discussion] Metrics Provider packages

I really like the idea of having OTEL as the metrics backbone for airflow. The flexibility and abstraction layer it offers really opens a lot of opportunities. I share Jarek's feelings for the current Statsd/Datadog situation, writing 2 custom collectors that will ensure backward compatibility see

Re: Request for feedback on proposal for new OpenLineage provider in Airflow

Same here if you can add me please. Looking forward to this session. Le mer. 22 mars 2023 à 23:07, Mehta, Shubham a écrit : > Please include me, I will try my best to join (shubhammehta...@gmail.com) > > Best, > Shubham > > On 2023-03-22, 2:24 PM, "Jarek Potiuk" ja...@potiuk.com>> wrote: > >

Re: [DISCUSS] AIP-52 updates - setup / teardown tasks

I am also in favor of explicit relationships only. >From a person who didn't work on AIP-52, it seems easier to understand what is going on without having to dive into the setup/teardown documentation. Le jeu. 23 mars 2023 à 22:53, Jed Cunningham a écrit : > I've been working closely with Danie

[VOTE] Release Airflow 2.5.3 from 2.5.3rc1

#29936) - Fix some punctuation and grammar (#29342) Cheers, Pierre Jeambrun

Re: [VOTE] Release Airflow 2.5.3 from 2.5.3rc1

B 14000; > > Aufsichtsratsvorsitzender: Prof. Dr. Stefan Asenkerschbaumer; > Geschäftsführung: Dr. Stefan Hartung, > > Dr. Christian Fischer, Filiz Albrecht, Dr. Markus Forschner, Dr. Markus > Heyn, Dr. Tanja Rückert > > > > -Original Message- > > Fro

Re: [VOTE] Release Airflow 2.5.3 from 2.5.3rc1

*Indeed the milestone for that *issue* was wrong. Le mar. 28 mars 2023 à 21:02, Pierre Jeambrun a écrit : > Hello Jens, > > Indeed the milestone for that PR was wrong. Thanks Jarek for fixing that. > > I also updated milestones for similar issues that will not be fixed in > 2

Re: [VOTE] March PR of the Month

There are a lot of great PRs this month, my vote goes to 29413 that I find amazing. Le mar. 28 mars 2023 à 21:03, Ferruzzi, Dennis a écrit : > Having poked at the KubernetesPodOperator in the past and knowing what a > bear it is to work with, I'll throw my vote to 28336. > > > - ferruzzi > > >

Re: [VOTE] Release Airflow 2.5.3 from 2.5.3rc1

te annoying, personally I wouldn't upgrade to 2.5.3 > if we keep it like that and would rather wait for 2.5.4, but +1 to fix it > in 2.5.3rc2. > > ____ > From: Pierre Jeambrun > Sent: Tuesday, March 28, 2023 9:03:34 PM > To: dev@airflow.apache.org > S

[VOTE] Release Airflow 2.5.3 from 2.5.3rc2

ally release. Release Notes: https://github.com/apache/airflow/blob/2.5.3rc2/RELEASE_NOTES.rst Changes since 2.5.3rc1: *Bug Fixes:* - Fix some long known Graph View UI problems (#29971, *#30355, #30360*) *Misc/Internal:* - None *Doc only changes:* - None Cheers, Pierre Jeambrun

[RESULT][VOTE] Release Airflow 2.5.3 from 2.5.3rc2

Hello, Apache Airflow 2.5.3 (based on RC2) has been accepted. 5 "+1" binding votes received: - Brent Bovenzi - Jarek Potiuk - Elad Kalif - Kaxil Naik - Pierre Jeambrun 3 "+1" non-binding votes received: - Josh Fell - Pankaj Singh - Hussein Awala Vote thread: https://lis

[ANNOUNCE] Apache Airflow 2.5.3 Released

lease notes here for more details: https://airflow.apache.org/docs/apache-airflow/2.5.3/release_notes.html Container images are published at: https://hub.docker.com/r/apache/airflow/tags/?page=1&name=2.5.3 Cheers, Pierre Jeambrun

Re: [VOTE] Airflow Providers prepared on April 02, 2023

+1 (binding). Verified checksums, signatures, licences, all looks good. Le mer. 5 avr. 2023 à 08:18, Pankaj Singh a écrit : > +1 non binding > > On Wed, Apr 5, 2023 at 10:19 AM Rajath Srinivasaiah > wrote: > > > +1 non binding > > > > Thanks and Regards, > > Rajath S > > rajath.srinivasa...@ast

Re: [ANNOUNCE] New committer Hussein Awala

Congratulations Hussein, well deserved ! On Tue 11 Apr 2023 at 23:51, Jarek Potiuk wrote: > Hello Airflow Community, > > I am happy to announce that the Project Management Committee > (PMC) for Apache Airflow has invited Hussein Awala > (github nickname hussein-awala) to become a > committer and

Re: [PROPOSAL] Archiving some old repos

+1 Le sam. 22 avr. 2023 à 08:51, Jarek Potiuk a écrit : > Hello everyone, > > We have a few old unused git repositories that have been used in the past > but now are defunct. Some of the old repos are marked as "archived" (i.e. > read-only and with the "public archive" banner - for example this

Re: [VOTE] Release Airflow 2.6.0 from 2.6.0rc1

+1 (binding), tested my changes, verified licences, checksum and signatures, all looks good. Le lun. 24 avr. 2023 à 16:08, Pankaj Koti a écrit : > +1 non-binding. We tested our asynchronous providers' DAGs for multiple > providers. > Regards, > > > > Pankaj Koti > > *Senior Software Engineer, *O

Re: [VOTE] April 2023 PR of the Month

+1 for #30175 Le mer. 26 avr. 2023 à 19:46, Phani Kumar a écrit : > +1 for #30705 > > On Wed, Apr 26, 2023 at 11:02 PM Hussein Awala wrote: > > > +1 for #30705 > > > > On Wed 26 Apr 2023 at 19:23, Pankaj Singh > > wrote: > > > > > +1 for #30705 as it has reduced CI execution drastically. > > >

Re: [VOTE] Release Airflow 2.6.0 from 2.6.0rc4

+1 (binding) checked signatures, licences and checksum, ran a few DAGs, looks good. Le ven. 28 avr. 2023 à 19:08, Josh Fell a écrit : > +1 (non-binding) > > On Fri, Apr 28, 2023 at 11:04 AM Hussein Awala wrote: > > > +1 (non-binding) > > > > On Fri 28 Apr 2023 at 18:03, Ash Berlin-Taylor wrot

Re: [VOTE] Release Airflow 2.6.0 from 2.6.0rc5

+1 binding. (licences, signatures, checksums and a few sample DAGs were fine) Le sam. 29 avr. 2023 à 15:09, Ash Berlin-Taylor a écrit : > +1 binding. > > I'm having flashbacks to the 1.9.0 release. > -ash > On Apr 29 2023, at 2:00 pm, Jarek Potiuk wrote: > > +1 binding. Checked licences, signat

Re: [VOTE] Release Airflow Python Client 2.6.0 from 2.6.0rc1

(+1 binding) Checked signatures and checksums, ran a few requests, looking good. Le mar. 2 mai 2023 à 10:31, Ephraim Anierobi a écrit : > Hey fellow Airflowers, > > I have cut the first release candidate for the Airflow Python Client > 2.6.0rc1. > The client consists of APIs corresponding to RES

Re: [VOTE] Release Airflow Python Client 2.6.0 from 2.6.0rc3

+1 (binding) Licenses, checksums and signatures look good. Also tried a few authenticated requests, running as expected. Le dim. 7 mai 2023 à 18:51, Ephraim Anierobi a écrit : > Hey fellow Airflowers, > > I have cut the first release candidate for the Airflow Python Client > 2.6.0rc3. > The clie

Re: [VOTE] Release Airflow Python Client 2.6.1 from 2.6.1rc1

+1 (binding), same. I don't think this is blocking but we have the `apache-airflow-client-2.6.0-source` archive inside the 2.6.1 source archive, must be some leftovers from the last release. Le dim. 21 mai 2023 à 11:24, Jarek Potiuk a écrit : > +1 (binding). Tested the client. checked licences,

Re: [ANNOUNCEMENT] Python 3.11 support merged for Apache Airflow

Well done, this is great! I looked around on other projects for similar compatibility patches (numpy, mypy, auto-sklearn etc...) and it seems there is no consensus on the question. (feature, enhancement, misc etc.) Excluding breeze image diff, the changeset is relatively small, I see no harm in p

Re: [LAZY CONSENSUS] define supporting older Python/Kubernetes versions as best efforts

Makes sense to me Le jeu. 25 mai 2023 à 10:00, Jarek Potiuk a écrit : > Just to add it: I am very strongly in favour of that one. We keep on > fighting with small problems caused by small issues that are creeping in > :). > > J > > On Thu, May 25, 2023 at 7:00 AM Elad Kalif wrote: > > > Hello e

Re: [ANNOUNCE] New committer: Pankaj Singh

Congratulations! On Tue 13 Jun 2023 at 02:30, Pankaj Koti wrote: > Many congratulations, Pankaj!! 🥳 > > On Tue, 13 Jun 2023, 05:38 Vikram Koka, > wrote: > > > Awesome! Congratulations Pankaj Singh! > > > > > > On Mon, Jun 12, 2023 at 3:37 PM Oliveira, Niko > > > > > wrote: > > > > > Woo! Congr

Re: [VOTE] Release Airflow 2.6.2 from 2.6.2rc2

+1 (binding), licences, checksums and signatures looks good to me. Tested my changes and ran a few DAGs. * Small typo, changes are from 2.6.2rc1 Le jeu. 15 juin 2023 à 00:40, Elad Kalif a écrit : > Hey fellow Airflowers, > > I have cut Airflow 2.6.2rc2. This email is calling a vote on the rel

[VOTE] Release Airflow Python Client 2.6.2 from 2.6.2rc1

*NEW API supported*: - NA Cheers, Pierre Jeambrun

Re: [VOTE] Release Airflow Python Client 2.6.2 from 2.6.2rc1

rc1 (I can reliably reproduce success/failure on just > switching between the two versions). > > No time to investigate it (I am host stage tomorrow at Berlin Buzzwords and > will be busy whole day) but I created an issue: > https://github.com/apache/airflow-client-python/issues/85 >

Re: [DISCUSS] Mechanism of SLA

This task_sla is more and more making me think of a ‘task’ on its own. It would need to be run in parallel, non blocking, not overlap between each other, etc… How hard would it be to spawn them when a task run with SLA configured as a normal workload on the worker ? Maybe on a dedicated queue / wo

[VOTE] Release Airflow Python Client 2.6.2 from 2.6.2rc2

o test the release and vote with "(non-binding)". *Changelog since 2.6.2rc1* *Major changes:* - NA *Major Fixes*: - NA *NEW API supported*: - NA Cheers, Pierre Jeambrun

Re: [VOTE] Release Airflow Python Client 2.6.2 from 2.6.2rc2

> > > Installed the RC and triggered an example DAG run. > >> > > > >> > > Regards, > >> > > > >> > > > >> > > > >> > > Pankaj Koti > >> > > > >> > > *Senior Software Eng

[RESULT]l[VOTE] Release Airflow Python Client 2.6.2 from 2.6.2rc2

Hello, Apache Airflow Python Client 2.6,2 (based on RC2) has been accepted. 3 "+1" binding votes received: - Ephraim Anierobi - Jarek Potiuk - Pierre Jeambrun 1 "+1" non-binding votes received: - Pankaj Koti - Utkarsh Sharma - Phani Kumar - Hussein Awala Vote thread: http

[ANNOUNCE] Apache Airflow Python Client 2.6.2 Released

tails: https://github.com/apache/airflow-client-python/blob/master/CHANGELOG.md Cheers, Pierre Jeambrun

Re: [ANNOUNCE] New committers: Vincent Beck, Phani Kumar, Maciej Obuchowski

Great news!!! Congratulations 🎉 On Wed 28 Jun 2023 at 18:40, Ankit Chaurasia wrote: > Congrats > > > > > > > > On Wed, Jun 28, 2023 at 10:09 PM utkarsh sharma > wrote: > > > Congratulations! :) > > > > On Wed, Jun 28, 2023 at 10:08 PM Oliveira, Niko > > > > wrote: > > > > > Congrats all! Very

Re: [ANNOUNCE] New committer: Dennis Ferruzzi

Congrats Dennis! On Wed 5 Jul 2023 at 09:07, Ankit Chaurasia wrote: > Congrats! > > > > > > > On Wed, Jul 5, 2023 at 12:30 PM Phani Kumar > wrote: > > > Congratulations Dennis ! > > > > On Wed, Jul 5, 2023 at 6:55 AM Wei Lee wrote: > > > > > Congratulations :) > > > > > > Best, > > > Wei > > >

Re: [VOTE] Release Airflow 2.6.3 from 2.6.3rc1

+1 (binding). Signatures, licences, checksums and artifacts vs tags look good. Also used it to run a few sample dags and played around with the UI. Le lun. 10 juil. 2023 à 17:59, Phani Kumar a écrit : > +1 non-binding. Ran some example DAGs and verified that they ran > successfully > > On Mon, J

Re: [VOTE] PR of the Month for the Airflow Newsletter

+1 for #31712 Le jeu. 27 juil. 2023 à 15:32, Collin McNulty a écrit : > +1 for 31712 > > On Thu, Jul 27, 2023 at 6:36 AM Phani Kumar > wrote: > > > +1 for #31712 > > > > On Thu, Jul 27, 2023 at 4:53 PM Pankaj Koti > > wrote: > > > > > +1 for #32525. > > > > > > Seems like a great contribution

Re: [VOTE] The daskexecutor, cncf.provider, celery providers in 2.7.0. as regular not-preinstalled providers

Option a On Sat 29 Jul 2023 at 22:39, Hussein Awala wrote: > I vote for option a > > On Sat 29 Jul 2023 at 21:57, Ash Berlin-Taylor wrote: > > > Option a. > > > > _ash > > > > On 29 July 2023 19:25:28 BST, Jarek Potiuk wrote: > > >Hello everyone, > > > > > >I would like to resume the vote disc

Re: [ANNOUNCE] New PMC member: Hussein Awala

Congratulations Hussein, well deserved! On Sat 29 Jul 2023 at 19:40, Pankaj Koti wrote: > Many congratulations, Hussein 🎉 🎉 🎉 > > On Sat, 29 Jul 2023, 23:06 Amogh Desai, wrote: > > > Awesome news! Good going, Hussein! > > > > Congratulations 🎉 > > > > Thanks, > > Amogh Desai > > > > On Sat, Ju

Re: [VOTE] Restore dag_run.conf UI triggering option for 2.7.0

+1 (binding) Le sam. 12 août 2023 à 19:50, Jarek Potiuk a écrit : > Tuesday 10am 15th (!) of August, 2023 of course, not 26th. That would be > quite a delay. > > On Sat, Aug 12, 2023 at 7:48 PM Hussein Awala wrote: > > > Thank you Jarek for raising this vote. > > > > +1 (binding) > > > > On Sat

Re: [VOTE] Release Airflow 2.7.0 from 2.7.0rc2

+1 (binding) Checksum, signatures, licences and release artifacts look good to me. Ran a few tests, working as expected. Le mer. 16 août 2023 à 21:48, Pankaj Singh a écrit : > +1 (non-binding) > > Ran astro-sdk tests and tested my changes. > > On Wed, Aug 16, 2023 at 11:23 PM Ferruzzi, Dennis >

Re: [DISCUSS] Drop MsSQL as supported backend

I am also in favor of dropping MSSQL. We have seen a lot of trouble with this particular backend, and with the data points you mentioned it definitely seems that it's not worth all the efforts to maintain it. Le ven. 18 août 2023 à 16:28, Wei Lee a écrit : > +1 (non binding) > > I agree with thi

Re: [VOTE] Release Airflow Python Client 2.7.0 from 2.7.0rc1

+1 binding - signatures, checksums, licences looks good. 2.7.0 client was expected to solve a few reported issues, (nullable refs). Tested those and it looks fine as well. Le mer. 23 août 2023 à 18:02, Jarek Potiuk a écrit : > +1 binding - checked signatures, checksums, run a few tests with air

Re: [VOTE] Drop MsSQL as supported backend

+1 (binding) Le lun. 28 août 2023 à 17:11, Vincent Beck a écrit : > +1 binding > > On 2023/08/28 07:55:17 Jarek Potiuk wrote: > > (just add that my voice is binding :) ) > > > > On Mon, Aug 28, 2023 at 9:35 AM Amogh Desai > > wrote: > > > > > +1 non binding > > > Based on previous discussions.

Re: [VOTE] August 2023 PR of the Month

Tough call, +1 for @eumiro work. On Wed 30 Aug 2023 at 04:06, Wei Lee wrote: > +1 to #30259 > > Best, > Wei > > > On Aug 30, 2023, at 12:59 AM, Frank Cash wrote: > > > > +1 to #30259. > > > > > > On Tue, Aug 29, 2023 at 1:27 AM Amogh Desai > > wrote: > > > >> Wasn't aware of things done by @eu

Re: [DISCUSS] move from semver to a more "rolling" release cycle for core

Same, I was very tempted by this at first but Jarek and Niko changed my mind. I think sticking to semver will be more beneficial in the long run. On Wed 30 Aug 2023 at 04:09, Mehta, Shubham wrote: > I couldn’t agree more with Jarek and Niko's perspective on the importance > of maintaining SemVer

Re: [DISCUSS] Preventing users from misusing _PIP_ADDITIONAL_REQUIREMENTS ?

Maybe we can introduce a global “DEBUG” config option/env variable. This could control some more verbose logging but most importantly only when this is turned on, we could use the sequential executor, debug executor, _PIP_ADDITIONAL_REQUIREMENTS and any other “debug/development” purpose options. L

Re: [ANNOUNCE] Pankaj Koti and Amogh Desai as committers

Congratulations to both of you, well deserved :) Le mer. 20 sept. 2023 à 00:50, Akash Sharma <2akash111...@gmail.com> a écrit : > Congrats Pankaj and Amogh. > > Best regards, > Akash > > On Tue, 19 Sep 2023, 23:33 Sameer Ahmad Siddiqui, < > sameerahmad@gmail.com> > wrote: > > > Congrats Panka

Re: [VOTE] September 2023 PR of the Month

+1 for 28900 On Fri 29 Sep 2023 at 23:14, Mehta, Shubham wrote: > + 1 to #28900. That required a lot of perseverance > > Shubham > > On 2023-09-29, 2:09 PM, "Briana Okyere" LID> wrote: > > > CAUTION: This email originated from outside of the organi

Re: [VOTE] Release Airflow Python Client 2.7.2 from 2.7.2rc1

+1 (binding). Licences, checksums and signatures look good. Also ran a few api requests against my local install, working as expected. Le ven. 13 oct. 2023 à 09:12, Ephraim Anierobi a écrit : > Hey fellow Airflowers, > > I have cut the release candidate for the Airflow Python Client 2.7.2rc1. >

Re: Airflow Docs Development Issues

+1 from moving archived docs outside of airflow-site. Even if that might mean a little more maintenance in case we need to propagate changes to all historical versions, we would have to handle 2 repositories, but that seems like a minor downside compared to the quality of life improvement that it

Re: The "no_status" state

Seems like a good idea. Some kind of "task diagnosis", in case the state is not settled to give more context to users. Happy to help on that one as well. I also think that a small AIP is required, the scope of change could be substantial. Best regards, Pierre Le jeu. 19 oct. 2023 à 17:05, Brent

Re: [DISCUSSION] Add 5 new Providers to enable first-class LLMOps

+1 from me as well. Indeed LLMs for Apache Airflow is a no brainer, this will open a lot of opportunities for our users. Having Astronomer supporting this initiative is great. I like the idea of system tests dashboard, especially for those that are not open source/easily testable without a paid a

  1   2   >