Re: [VOTE] Proposal for adding Telemetry via Scarf

+1 binding On Thu, 9 May 2024 at 12:40, Andrey Anshin wrote: > +1 binding > > > > > > On Thu, 9 May 2024 at 13:25, Wei Lee wrote: > > > Got it. Thanks Jarek for pointing out! > > > > Best, > > Wei > > > > > On May 9, 2024, at 3:59 PM, Ankit Chaurasia > wrote: > > > > > > +1 non-binding > > > >

Re: [ANNOUNCE] New committer: Wei Lee

Congrats! On Mon, 8 Apr 2024 at 19:56, Ankit Chaurasia wrote: > Congratulations Wei > > *Ankit Chaurasia* > HomePage | LinkedIn > > > > > > > > On Mon, 8 Apr 2024 at 23:38, Pierre Jeambrun > wrote: > > > Congratulations! >

Re: [ANNOUNCE] New committer Hussein Awala

Congratulations! T. On Wed, 12 Apr 2023 at 15:12, Bowrna Prabhakaran wrote: > Congratulations Hussein!! > > On Wed, Apr 12, 2023 at 1:47 PM Jean Eudes PELOYE > wrote: > > > Congratulations Hussein! > > > > On Wed, 12 Apr 2023 at 04:02, Ferruzzi, Dennis > > > > > wrote: > > > > > Congrats! > >

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

+1 binding,I like the idea! T. On Sat, 24 Dec 2022 at 15:45, Pierre Jeambrun wrote: > +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 Ma

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

Congrats Andrey! T.

Re: [VOTE] AIP-51 - Removing Executor Coupling from Core Airlfow

+1 binding. I personally added some of the coupling ifs😀 T.

Re: [Discussion] Airflow Newsletter name and branding

Atmosphere +1! T.

Re: [ANNOUNCEMENT] Breeze rewrite to Python finally completed !!! Congrats to Bowrna, Edith (and Elad as mentor)!

Amazing work, kudos to everyone involved! The less bash the better :D T. On Tue, 4 Oct 2022 at 15:05, Josh Fell wrote: > Yes, the new Breeze is amazing! Really great work Bowrna, Edith, Jarek, > and Elad 🎉 > > On Tue, Oct 4, 2022 at 3:27 AM Sumit Maheshwari > wrote: > >> Awesome work Bowrna, E

Re: [ANNOUNCE] New PMC member: Daniel Standish

Well deserved Daniel, congrats! T. On Thu, 22 Sept 2022 at 18:10, Josh Fell wrote: > Congrats Daniel! > > On Thu, Sep 22, 2022 at 10:23 AM Vikram Koka > wrote: > >> Congratulations Daniel! Very well deserved! >> >> On Thu, Sep 22, 2022 at 12:57 AM Jarek Potiuk wrote: >> >>> Hello Airflow Comm

Re: [ANNOUNCE] New PMC member: Tzu-ping Chung

Congratulations TP, well deserved! T. On Thu, 22 Sept 2022 at 18:10, Josh Fell wrote: > Congrats TP! > > On Thu, Sep 22, 2022 at 10:22 AM Vikram Koka > wrote: > >> Congratulations TP! Very well deserved! >> >> Vikram >> >> >> On Thu, Sep 22, 2022 at 12:55 AM Jarek Potiuk wrote: >> >>> Hello A

Re: [ANNOUNCE] New Committer: Pierre Jeaambrun

Congrats Pierre! T. On Thu, 22 Sept 2022 at 17:54, Vikram Koka wrote: > Congratulations Pierre! Very well deserved > > > On Thu, Sep 22, 2022 at 8:35 AM Josh Fell > wrote: > >> Here here! Congrats Pierre! >> >> On Thu, Sep 22, 2022 at 8:10 AM Brent Bovenzi >> wrote: >> >>> Congratulations Pie

2022 ASF Community Survey

Hello everyone, The 2022 ASF Community Survey is looking to gather scientific data that allows us to understand our community better, both in its demographic composition, and also in collaboration styles and preferences. We want to find areas where we can continue to do great work, and others wher

Re: Airflow Pluggable Scheduler

Hey Ping, I somehow agree with Jarek that there's not much detail on what exactly would be the "pluggable" part. Is "new" scheduler the only solution to those problems you have mentioned? As said, maybe we should consider DagRuns prioritisation? If growing tables is a perf problem then maybe you

Re: [Proposal] Creating DAG through the REST api

In general I second what XD said. CI/CD feels better than sending DAG files over API and the security issues arising from accepting "any python file" are probably quite big. However, I think this proposal can be tightly related to "declarative DAGs". Instead of sending a DAG file, the user would s

Re: [VOTE] AIP-49 OpenTelemetry Support for Apache Airflow

+1 (binding), OpenTelemetry is great! On Tue, 14 Jun 2022 at 22:14, Jarek Potiuk wrote: > Big +1 (binding) from me. I took part in preparing it and I see more and > more need from users who want it. > > On Tue, Jun 14, 2022 at 6:26 PM Howard Yoo wrote: > >> Now that Summit is over (well done

Re: Airflow Survey Writeup Draft

faulted to a full presentation of the results. If you think it's a bit > much we can do a series of posts talking about each section, and have one > initial post covering the TL;DR, an expanded executive summary, and the raw > data link > > Regards, > John > > On Mon, Ju

Re: Airflow Survey Writeup Draft

Thanks John! I really love the TL;DR! The doc has 31 pages, I'm wondering if that's not too much for a blog post. I've left few comments. Cheers, Tomek On Mon, 13 Jun 2022 at 21:57, John Thomas wrote: > Hi All, > > Here's the draft of the airflow survey's initial writeup! Take a look and > l

Re: [VOTE] AIP-48 Data Driven Scheduling

+1 (binding) On Thu, 2 Jun 2022 at 15:49, Josh Fell wrote: > +1 (binding) > > On Thu, Jun 2, 2022 at 9:31 AM Hila Sofer Elyashiv > wrote: > >> +1 non-binding >> >> On 2022/06/01 16:34:13 Ash Berlin-Taylor wrote: >> > Hi All, >> > >> > Now that Summit is over (well done all the speakers! The tal

New Committer: Ping Zhang

Hello Airflow Community, The Project Management Committee (PMC) for Apache Airflow has invited *Ping Zhang* to become Airflow committers and we are pleased to announce that he has accepted! Congratulations Ping, welcome aboard! Bests, Tomek on behalf of Airflow PMC

Re: 2022 Airflow User Survey Planning

Thanks John for starting this work! I left some comments in the doc. Cheers, tomek On Fri, 29 Apr 2022 at 19:23, John Thomas wrote: > Hi Folks! > > In 2019 and 2020 > we did surveys to get a > go

Re: [DISCUSS] Approach for new providers of the community

I’m leaning toward Ash approach. Having providers maintaining the packages may streamline many aspects for providers/companies. 1. They are owners so they can merge and release whenever they need. 2. It’s easier for them to add E2E tests and manage the resources needed for running them. 3. The dev

Add retry option for TaskGroup

Hey folks, There's an interesting feature request for retry option on TaskGroup level: https://github.com/apache/airflow/discussions/21333 I'm not sure if we can handle this nicely. Any opinions would be welcome! Cheers, Tomek

Re: [LAZY CONSENSUS] Deprecate non-JSON extra, and require a dict

> > Should we provide some way of validating existing connections so users can check this before upgrading to 3.0? > Sounds like a good idea I think we may consider refreshing the airflow upgrade scripts On Fri, 25 Feb 2022 at 22:04, Daniel Standish wrote: > > What does this mean for the extra

Re: [LAZY CONSENSUS] Deprecate non-JSON extra, and require a dict

+1 for this idea. Should we provide some way of validating existing connections so users can check this before upgrading to 3.0? Thanks, Tomek On Fri, 25 Feb 2022 at 10:14, Ash Berlin-Taylor wrote: > I'm all for this. > > What does this mean for the extra and extra_dejson attrs that exist on >

Re: [DISCUSS] Converting airflow's CLI to "click" and "rich_click" External Inbox airflow-dev

+1 for the idea, I’ve used click for few clis and the experience is definitely better than argparse. Integration with rich is an additional advantage.

Re: New Commiter: Malthe Borch

Congratulations Malthe!

Re: New committer: Josh Fell

Congrats Josh!

Re: [VOTE] AIP-47 New design of Airflow System Tests

+1 (binding) Tomek

Re: [DISCUSS] how to name classes with abbreviations?

+1 for BranchSqlOperator, easier to read imho On Fri, 4 Feb 2022 at 20:39, Howard Yoo wrote: > Just my two cents : Have preference for not capitalizing all the > characters in abbrevications, so > BranchSqlOperator is totally fine with me. It's also easier to type (less > pressing on Caps key!),

Re: [VOTE] deprecate days_ago helper function

+1 binding. Just please make sure we do point to resources for keeping equivalent behaviour. On Fri, 4 Feb 2022 at 16:14, Arthur Wiedmer wrote: > +1 (binding) > > On Thu, Feb 3, 2022, 17:03 Daniel Standish > wrote: > >> Hi >> >> I would like to call a vote on the following proposal: >> >> Helpe

Re: Apache Airflow Community Survey 2021

Hey Tatiana, Happy to help you with the survey this year! In previous years we used Google forms and before publishing the survey we usually brainstormed what should be in the form, here's the link to discussion from 2020: https://lists.apache.org/thread/95078q50mpg3gwonczhhg0h846xv9lgg > How hav

Re: New PMC Member: Jed Cunningham

Congratulations Jed! On Wed, 5 Jan 2022 at 03:37, Ian Stanton wrote: > Congrats Jed! > > On Tue, Jan 4, 2022, 4:01 PM Dennis Akpenyi > wrote: > >> Congratulations Jed! Well deserved! >> >> On Tue 4. Jan 2022 at 21:56, Kevin Yang wrote: >> >>> Congrats Jed 👍 >>> >>> On Tue, Jan 4, 2022 at 10:3

Re: [PROPOSAL] Removal of Python2 "virtualenv" support in Airlfow 2.3 ?

+1 On Tue, 21 Dec 2021 at 16:19, Elad Kalif wrote: > +1 > > On Tue, Dec 21, 2021 at 4:02 PM Ash Berlin-Taylor wrote: > >> +1 >> >> On 21 December 2021 13:41:53 GMT, Jarek Potiuk wrote: >>> >>> Following the discussion in >>> https://github.com/apache/airflow/pull/20238#issuecomment-998780796 >

Re: [LAZY CONSENSUS] Smart Sensors - Deprecation and removal

Do we have documentation about how to migrate from smart sensors to deferrable operators?

Re: [VOTE] AIP-42 Dynamic Task Mapping

+1 (binding), love the idea!

Re: [ANNOUNCE] Airflow 2.2.0 is released

Well done everyone! 👏 On Tue, 12 Oct 2021 at 08:02, Sumit Maheshwari wrote: > Awesome 👏 > > On Tue, Oct 12, 2021 at 11:13 AM Kaxil Naik wrote: > >> That's another big milestone for Airflow. >> >> Thank you to everyone who contributed to this release and Jed for >> steering this release. >> >> R

Re: [VOTE] Release Airflow 2.1.4 from 2.1.4rc1

+1 binding On Wed, 15 Sept 2021 at 13:44, Dennis Akpenyi wrote: > +1 non-binding > > On Wed 15. Sep 2021 at 13:33, Ash Berlin-Taylor wrote: > >> +1 binding >> >> On Tue, Sep 14 2021 at 20:44:02 -0400, Josh Fell >> wrote: >> >> +1 (non-binding) - Verified a few bug fixes and tested with a numbe

Re: New PMC Members: Ephraim Anierobi & Elad Kalif

Congrats! Well deserved!

Re: [DISCUSS] Add "new version available" indicator to UI/CLI ?

I think this can be a really useful feature. Especially for those who manage Airflow deployments on their own. > 3) How "annoying" and "how often" should it be shown ? Should you be able to dismiss it? For some time maybe ? Till next release? I think per release update should be enough and users

Re: New Committer: Brent Bovenzi

Congrats Brent!

Re: Issue form for Bugs/features in GitHub

o work out the right template where people will HAVE TO >> choose an area when they submit a bug. There are some "drop-down" fields >> you can define, there are some "required" fields that you have to fill-in. >> I think it's a great possibility to do a

Re: Issue form for Bugs/features in GitHub

According to this link the feature is in beta, isn’t it? Maybe it will work out of the box but GitHub often enrolls repos/orgs for betas. T.

Re: Issue form for Bugs/features in GitHub

This works for any type of issues, KEDA is also using it for a long time: https://github.com/kedacore/keda/issues/new/choose But from what I remember that was a beta feature enabled on a repo/org basis, has it changed? If yes then I think we should enable it. Tomek On Thu, 19 Aug 2021 at 19:16,

Re: New Committer: Aneesh Joseph

Congrats Aneesh! On Wed, 7 Jul 2021 at 16:42, Dennis Akpenyi wrote: > Congratulations Aneesh! > > On Wed, Jul 7, 2021 at 4:19 PM Vikram Koka > wrote: > >> Congratulations Aneesh! >> >> >> On Wed, Jul 7, 2021 at 2:34 AM Elad Kalif wrote: >> >>> Congrats! Welcome aboard :) >>> >>> On Tue, Jul 6

Re: New Committers: Jed Cunningham & Tzu-ping Chung

Congrats Jed & Tzu-ping!! Tomek On Tue, 29 Jun 2021 at 15:45, Bas Harenslak wrote: > Congrats both Jed & Tzu-ping! > > Cheers, > Bas > > On 29 Jun 2021, at 03:48, Jiajie Zhong wrote: > > Congratulations Jed and Tzu-ping! > > Best Wish > — Jiajie > > >

Re: [VOTE] Disable pylint ?

too-many-statements # pylint: disable=undefined-variable # pylint: > disable=unexpected-keyword-arg # pylint: disable=ungrouped-imports # > pylint: disable=unidiomatic-typecheck # pylint: disable=unnecessary-lambda > # pylint: disable=unsubscriptable-object # pylint: > disable=unsupported-m

Re: [VOTE] Disable pylint ?

-0.5 from me. Black and flake8 does not guarantee the same quality and consistency of code as pylint (for example using if list instead of if len(list) > 0 ). > I can't remember the last time where pylint prevented any real error Well, isn't it a survivor bias (the one usually represented by this

Re: [DISCUSS] Managing provider Connections via UI in managed Airflow services

> However I still don't really understand the risk - if dag authors can write dags they can run a python operator to do what ever they like. How are plugins different? > The main thing I can't wrap my head around why suitably permissioned users can't have the ability to customise the webserver imag

Re: Roadmap ideas for Airflow 2.2 and beyond

+1 to Rob suggestion. I would also add a task callback "on delay" that would work better than the current SLA mechanism. For example I have a task scheduled daily, but the task should not take more than 5 minutes (but I don't want to set timeout) and I would like to get an email if the task last l

Re: [DISCUSS] Using semantic/conventional commits in Airflow?

Related discussion from last year ("Use semantic pull request"): https://lists.apache.org/thread.html/r076232c60600238f37277497f66fb7eb9507869b92403c5ef96dcb3e%40%3Cdev.airflow.apache.org%3E On Sun, 13 Jun 2021 at 12:56, Jarek Potiuk wrote: > > Hey everyone, > > I would like to hear people's opi

Re: [DRAFT of NEWSLETTER] What happened in April and May 2021?

Thanks Karolina! Added my two cents about 1.10 EOL and new committers. On Wed, 9 Jun 2021 at 19:57, Karolina wrote: > Hello everyone, > > First of all, sorry to have kept you waiting so long for the Airflow news > and cats' pics in the newsletter. During the last two months I focused on > my men

Re: Allyship workshops for open source contributors

+1 On Wed, 9 Jun 2021 at 18:29, Alex Liotta wrote: > +1 > > On Tue, Jun 8, 2021 at 9:50 PM Vikram Koka > wrote: > >> +1 >> >> >> On Fri, Jun 4, 2021 at 6:49 AM Jake Ferriero >> wrote: >> >>> +1 >>> >>> On Thu, Jun 3, 2021 at 6:09 PM Paola Peraza Calderon >>> wrote: >>> +1 On Th

Re: Renaming master branch to main is now done.

Nice job! Thanks Ash and Jarek for leading this effort. Tomek On Tue, 1 Jun 2021 at 14:38, Alexander Shorin wrote: > > It's such a pity. > > -- > ,,,^..^,,, > > > On Tue, Jun 1, 2021 at 1:06 PM Ash Berlin-Taylor wrote: >> >> Hi everyone, >> >> This rename has now happened, and the default brach

Re: MSSQL compatbility for Airflow, YAY!

Big kudos to all who contributed to this! Thanks Aneesh! On Wed, 26 May 2021 at 15:58, Ry Walker wrote: > That is - how MSSQL performs w/ Airflow (not in general). > And also, nice work Aneesh! > > On Wed, May 26, 2021 at 9:56 AM Ry Walker wrote: > >> Curious - was any performance analysis done

Re: [ANNOUNCE] Apache Airflow Helm Chart version 1.0.0 Released

Big kudos to everyone who enabled that! On Thu, 20 May 2021 at 10:37, Jarek Potiuk wrote: > Great! This is a major step forward for the community! > > On Thu, May 20, 2021 at 4:57 AM Vikram Koka > wrote: > >> Awesome! >> Great job Kaxil and everyone who contributed to this! >> >> On Wed, May 19

Re: [VOTE] Release Airflow 2.1.0 from RC2

+1 binding On Wed, 19 May 2021 at 01:00, James Timmins wrote: > > +1 (non-binding) > On May 18, 2021, 8:03 AM -0700, Nathan Hadfield , > wrote: > > +1 (non-binding) > > • Verified running lots of our production DAGs against GCP, AWS and external > APIs. > • I also love calendar view and the r

Re: [VOTE] Airflow Providers - release prepared 2021-05-01

+1, checked checksums, signatures and licenses On Wed, 5 May 2021 at 20:50, Jarek Potiuk wrote: > > Hello everyone, > > Voting time ends soon. Most of the providers have been tested > https://github.com/apache/airflow/issues/15623#issuecomment-832883599 . Need > two more PMC votes. > > On Sat,

Re: Add Downloads page at Airflow Apache website?

+1 for the idea. I think this would be another way we can emphasize the core/providers split and definitely. Probably we may consider pointing to external providers, but not sure how this is aligned with ASF rules. Cheers, Tomek On Tue, 4 May 2021 at 13:00, Jarek Potiuk wrote: > > Hello everyone

Re: [VOTE] AIP-40: Deferrable ("Async") Operators

+1 binding - love the idea! On Fri, 30 Apr 2021 at 10:40, Jarek Potiuk wrote: > > +1 (binding) > > On Fri, Apr 30, 2021 at 10:29 AM Ash Berlin-Taylor wrote: > > > > +1 (binding) > > > > On Thu, Apr 29 2021 at 18:32:23 -0700, Daniel Imberman > > wrote: > > > > +1 (binding) > > > > I’m really ex

Re: Apache Airflow newsletter - March 2021

Thanks Karolina for such a great update! On Sat, 17 Apr 2021 at 09:57, Karolina wrote: > Apache Airflow newsletter for anyone too busy to read the devlist. > > View email in your browser > > *Apache Airflow newsletter* > >

Re: Triage role for Jed Cunnigham

+1 On Sun, 11 Apr 2021 at 00:59, Daniel Imberman wrote: > > +1 > > On Sat, Apr 10, 2021 at 3:54 PM, Ryan Hamilton > wrote: > > +1 > > On Sat, Apr 10, 2021 at 6:45 PM Kaxil Naik wrote: >> >> Hi folks, >> >> I would like to propose that the triage role be given to Jed Cunnigham >> (Github Handl

Re: [VOTE] Airflow Providers - release prepared 2021-04-07

+1 binding On Fri, 9 Apr 2021 at 23:25, Xiaodong Deng wrote: > > +1 (binding). > > Thanks Jarek and folks who help test. > > > XD > > On Fri, Apr 9, 2021 at 10:23 Jarek Potiuk wrote: >> >> I'd appreciate some votes/checks - also see the >> https://github.com/apache/airflow/issues/15241 for sta

Re: [VOTE] Airflow Backport Providers (http only) 2021.4.10rc2

+1 binding On Sat, 10 Apr 2021 at 11:29, Jarek Potiuk wrote: > > One more vote needed. Also it's been confirmed that it works by the user who > raised the issue : > https://github.com/apache/airflow/issues/15198#issuecomment-815382368 > > On Sat, Apr 10, 2021 at 1:17 AM Kaxil Naik wrote: >> >>

Re: New Committers: Qian Yu & Xinbin Huang

Congrats to both of you! On Tue, 6 Apr 2021 at 19:34, Jarek Potiuk wrote: > Cool! > > wt., 6 kwi 2021, 16:42 użytkownik Daniel Standish > napisał: > >> Congrats! 👏 >> >

Re: [DISCUSS] Guidelines for Releasing Providers packages

tools. >>>> >>>> However, I think we can do a different thing in this case. I do not think >>>> we strictly need to release the packages when we see doc-only change. What >>>> we can do - we can simply tag it with *-doc1, *-doc2 tags in the repo

Re: Call for Presentations for ApacheCon 2021 now open

Hey Ace, I think it depends what audience you want to target. During the Airflow Summit it will be mostly Airflow users, during ApacheCon it will be a variety of folks. As far as I know we do not plan to have an Airflow track during ApacheCon. However, there's a BigData track. If I may suggest som

Re: Triage role for active contributors

+1 for that. I don't think we need a vote but it's good to have approval on the dev list as we should link it in the JIRA issue requesting the triage roel. Tomek On Wed, 24 Mar 2021 at 00:30, Ryan Hamilton wrote: > Could we grant this triage role for Brent Bovenzi ( > https://github.com/bbovenz

Re: [VOTE] Airflow Backport Providers 2021.3.17rc1

+1 binding Checked licenses, checksums and signatures. I was able to install all providers but odbc in apache/airflow:1.10.14 docker image. The odbc backport failed on missing gcc - but imho this is not a blocker for release as users can instal gcc in their images if necessary. On Sun, 14 Mar 202

Re: [VOTE] Apache Airflow Elasticsearch Provider 1.0.3

+1 binding Verified licenses and signatures. Thanks Kaxil! On Sat, 13 Mar 2021 at 22:36, Kaxil Naik wrote: > > The only change in this version of Elastic Search provider compared to 1.0.2 > version is > https://github.com/apache/airflow/commit/923bde2b917099135adfe470a5453f663131fd5f > > Regar

Re: [VOTE] Release Apache Airflow 1.10.15 based on 1.10.15rc1

+1 (binding) Verified licenses, checksums and signatures. Successfully updated from 1.10.14. Run successfully a few example DAGs with no issues. Clicked through web ui (docs are not working but that's expected). Tomek

Re: [VOTE] Airflow Backport Providers 2021.3.13rc1

+1 (binding) Checked signatures, checksums and licenses. Installed all packages with Airflow 1.10.14. Tomek On Sat, 13 Mar 2021 at 10:42, Jarek Potiuk wrote: > Cool. Thanks Kaxil. One more evite to go :) > > pt., 12 mar 2021, 23:26 użytkownik Kaxil Naik > napisał: > >> +1 (binding) >> >> Veri

Re: [DISCUSS][AIP-39] Richer (and pluggable) schedule_interval on DAGs

> Timetable is a synonym of ’Schedule’ I'm not a native speaker and I don't get it easily as a synonym. To be honest the "timetable" sounds like a complex piece of software. Personally I experienced that people use schedule and schedule_interval interchangeably. Additionally, schedule being more

Re: [VOTE] Release apache-airflow-upgrade-check 1.3.0 from 1.3.0rc2

+1 binding On Thu, 11 Mar 2021 at 12:13, Ash Berlin-Taylor wrote: > +1 binding > > > Checked sigs/sums and diff from rc1. Simple test works too. > > On Thu, 11 Mar, 2021 at 12:38, Elad Kalif wrote: > > + 1 (non-binding) > Verified issue from RC1 is resolved. > > On Thu, Mar 11, 2021 at 12:29 AM

Re: [VOTE] Airflow Providers - release prepared 2021-03-08

l with the same "calver" version. > In the backport providers sdist we have the modified (automatically > generated) code not the source. So having a separate source package from > which the backports were generated as "official" sources matching the git > tag makes

Re: [VOTE] Airflow Providers - release prepared 2021-03-08

According to SVN check step there should be 36 (4 x 9) files. I see all whl files but instead of: -bin-tar.gz + .asc + .sha512 (one set of files per provider) I see: -tar.gz + .asc + .sha512 And no source.tar.gz + .asc + .sha512 (one set of files) [unless we count the ones from backports). Is th

Re: [DISCUSS] Guidelines for Releasing Providers packages

I'm ok with batch and ad-hoc approach as well as with the frequency. In case of docs-only changes I second what Ash proposed - let's not alter the version. 100% of functionality is the same so users are not affected and there's no need to update. As per testing I agree that E2E testing of all pro

Re: [DISCUSS] Major Version should contain new features or just removal of deprecation?

I'm also in favor of *b)*. If we expect that new features may confuse users then maybe we should adopt a rule that when a feature is introduced it is protected by the feature flag and is not enabled by default. Of course this may not always be possible or may create even more confusion. Cheers, T

Re: [Meeting Notes] Airflow Dev Call - 3 March 2021

Thanks Kaxil for the notes! Tomek On Mon, 8 Mar 2021 at 22:41, Kaxil Naik wrote: > > Hi all, > > Here are the notes from our Airflow dev call last week. Thank you to all who > joined the call. > Here is a quick summary of the call. > > Summary Notes: > > Add a policy document around all our Pol

Re: [VOTE] AIP-38: Modern Web Application

+1 (binding). Amazing work! On Wed, 3 Mar 2021 at 22:23, Euccas Chen wrote: > +1 (non-binding) > > On Wed, Mar 3, 2021 at 11:23 AM Xinbin Huang > wrote: > >> +1 (non-binding) >> >> On Wed, Mar 3, 2021 at 10:37 AM Gerard Casas Saez >> wrote: >> >>> +1 (non-binding) Really excited for this! Look

Re: New Committers: James Timmins, Elad Kalif & Daniel Standish

Congrats Elad, Daniel and James! Well deserved indeed! T. On Mon, 1 Mar 2021 at 19:12, Jarek Potiuk wrote: > Woohoo! > > On Mon, Mar 1, 2021 at 6:04 PM Sumit Maheshwari > wrote: > >> Congratulations to all!! >> >> On Mon, Mar 1, 2021 at 9:26 PM Felix Uellendall >> wrote: >> >>> Congrats! Well

Re: Create official Apache Airflow publication on Medium.com

the publication. > This is right up my alley - I love proofreading! :) > > On Tue, Feb 23, 2021 at 4:41 AM Tobiasz Kędzierski < > tobiaszkedzier...@gmail.com> wrote: > >> It is great! I've just added to my bookmarks. >> >> Thanks Tomek! >> >

Re: Article on Medium

Hey Ashish, It's a nice article! I added you as a writer to the publication. Cheers, Tomek On Tue, 23 Feb 2021 at 19:14, Ashish Kumar wrote: > Hi, > Firstly, welcome to medium :) > > I am Ashish, and a few months back, I wrote a very small article on > Airflow for the issue I personally faced

Re: New Airflow Committer: Ephraim Anierobi

Congratulations Ephraim! 🚀 T. On Tue, 23 Feb 2021 at 19:39, Ephraim Anierobi wrote: > Thanks everyone. I'm really excited about this! Looking forward to more > collaboration with you all. > > Regards > Ephraim > > On Tue, 23 Feb 2021, 19:35 Daniel Standish, wrote: > >> congrats 👏 >> >> On Tue,

Re: [Newsletter] Follow-up after 3 newsletters

This is an interesting idea to have the newsletter published as a blog post. Definitely easier to find for those who are not on the dev list. T. On Tue, 23 Feb 2021 at 15:50, Alex Inhert wrote: > I really like the newsletter but I think it's better to be as a monthly > blog post rather than som

Re: Create official Apache Airflow publication on Medium.com

Hello all, As promised I created the publication: https://medium.com/apache-airflow If you know some articles that we can add to the publication - let me know, here or on #blogposts channel on Airflow slack. Committers - if you are interested in being editor, please provide (can be via slack) yo

Re: Create official Apache Airflow publication on Medium.com

Iuliia that's also my understanding that articles are only behind paywall if authors will want it. Most tech blog posts are rather free of charge (at least I never hit "upgrade to read" reading those). So I think this is not a blocker. Especially that my main point of this proposal was to create an

Re: Create official Apache Airflow publication on Medium.com

dea and let's get started on it. >> >> Regards, >> Hitesh Gupta >> >> On Sun, Feb 21, 2021, 7:00 AM Mara Ruvalcaba wrote: >>> >>> Great idea Tomek, medium is a very used platform, I know a lot of people >>> write there/read it. >>> &

Re: Create official Apache Airflow publication on Medium.com

But indeed if there would be some people (like Ryan) willing to not only review but help authors edit/improve the articles it would be awesome. T. On Sat, 20 Feb 2021 at 19:03, Tomasz Urbaszek wrote: > > I was thinking that we may start with granting "accept right" to the >

Re: Create official Apache Airflow publication on Medium.com

uk wrote: >> >> I think this is a great idea. I did not know that "publication" exists, but >> I think it perfectly fits the purpose, reading the description. >> >> J. >> >> >> On Sat, Feb 20, 2021 at 7:41 AM Tomasz Urbaszek wrote: >>&

Create official Apache Airflow publication on Medium.com

Hello, Currently our community have a blog on our official website: http://airflow.apache.org/blog/ But I was wondering if it would make sense to create official Apache Airflow publication on medium.com which is much more often used for publishing blogspot: https://help.medium.com/hc/en-us/articl

Re: [Newsletter] Follow-up after 3 newsletters

Personally I think the newsletter was an amazing source of information (and cats) and it would be lovely to keep it up! Tomek On Wed, 17 Feb 2021 at 18:25, Karolina wrote: > Hello everyone! > > Long time no see. I'm getting back to ask all of you what are your > thoughts about the newsletter so

Re: [VOTE] Release Apache Airflow 2.0.1 from 2.0.1rc2

+1 (binding) Tested locally and in a staging environment (tested only postgres). I can confirm that the SLA mechanism was fixed and I found no new issues. Tomek On Mon, 8 Feb 2021 at 19:56, Jarek Potiuk wrote: > > +1 (binding). > > * tested the signature/licences/checksum. > * tested airflow wi

Re: [VOTE] Airflow Providers - release done 2021-02-04

+1 binding - tested exasol, related s3 operator and new cloud workflows operators. Tomek On Thu, Feb 4, 2021 at 4:20 PM Jarek Potiuk wrote: > Hey all, > > I have just cut the new wave of the Airflow Providers packages. This > email is calling a vote on the release, > which will last for 72 hou

Re: Apache Airflow Community Survey 2020

Hi all, I would like to remind you that the survey is still open: https://forms.gle/PLVpjrqx5r6v1rw87 If you would like to share the link on your social medias it would be more than welcome ❤️ Cheers, Tomek On Tue, Jan 19, 2021 at 5:18 PM Tomasz Urbaszek wrote: > Hello all! > > I w

Apache Airflow Community Survey 2020

Hello all! I would like to encourage you to take part in *Apache Airflow Community Survey 2020*! This survey should not take more than 10 minutes and will help us understand you and your needs: https://forms.gle/PLVpjrqx5r6v1rw87 The results allow us to decide what should be the main focus of the

Re: Measuring community state

ammar. PTAL :). >>> via Newton Mail >>> <https://cloudmagic.com/k/d/mailapp?ct=dx&cv=10.0.51&pv=10.15.7&source=email_footer_2> >>> >>> On Thu, Jan 14, 2021 at 4:44 AM, Kaxil Naik wrote: >>> >>> Looks good to me, thanks Tomek.

Re: Measuring community state

Hi folks, I move the questions from doc to the google form: https://forms.gle/EZz8s5pGYDpHL2Ex8 Please let me know if there's something you would like to fix or add. I'm planning to send the survey out on Monday. Cheers, Tomek On Fri, Nov 20, 2020 at 10:47 AM Tomasz Urbaszek wrote

Re: Provider naming: Specifically Salesforce, Tableau and Slack

I'm in favor of separate packages for tableau and slack. Until now I didn't know they are owned by salesforce and I would not even dare to look for them in salesforce provider. In my opinion we should prefer user experience over "business correctness". While amazon and google are big and most of t

Re: Test style convention after migration to pytest

on't think we need to (yet) do any bulk changes to the test, but if we > agree that using more of pytest is the way to go then we can write new > tests using assert style, and once we've got a good chunk of the way we can > bulk switch the rest. > > -ash > > On Oct 22 20

Re: [DISCUSS] [AIP-37] Virtualenv management inside Airflow

smaller groups, the ability to see and interact with other people's dags >> via the UI - while also managing their own dependencies - would be a >> feature, not a bug. The Airflow UI, with descriptive dag and task ids, are >> a visual cue for the subgroups to speak with one

  1   2   3   4   >