Re: Consider using stale bot for issues

If I opened a bug report - what is the action expected from my side to keep it alive? Am I supposed to comment on it every 30 days? Check https://github.com/apache/airflow/pull/10760 was picked after being open for 3+ months. Keep in mind that not always the person who reports the issue also has t

Re: Consider using stale bot for issues

mine is @eladkal On Mon, Sep 14, 2020 at 4:33 AM Pete DeJoy wrote: > I’d love to help as well! Gh handle is @petedejoy > > Thanks for organizing everyone. > > Pete > On Sep 13, 2020, 4:57 PM -0400, Jarek Potiuk , > wrote: > > @Kamil Breguła - I believe we already base > it > > on the experience

Re: Consider using stale bot for issues

After reviewing some issues I think we might need a few more labels like: area:scheduling options missing information can't reproduce maybe we can create a dedicated slack channel to work on the small details. Elad On Wed, Sep 16, 2020 at 9:12 PM Kaxil Naik wrote: > @paola - Unfortunately the

Re: [VOTE] Airflow Providers prepared on August 10, 2022 (rc3)

+1 binding On Sat, Aug 13, 2022 at 10:36 PM Pankaj Singh wrote: > Tested my changes for AWS provider. > > +1 (non binding) > > On Sun, Aug 14, 2022 at 12:11 AM Phani Kumar > wrote: > >> +1 (non binding) >> >> On Sat, Aug 13, 2022 at 10:35 PM Jarek Potiuk wrote: >> >>> We need one more vote :)

Re: [VOTE] Airflow Providers prepared on August 15, 2022 (RC4)

+1 binding On Wed, Aug 17, 2022 at 12:45 PM Phani Kumar wrote: > +1 (non binding). Our databricks DAG ran fine with the databricks 3.2.0rc4 > > On Tue, Aug 16, 2022 at 5:10 PM Ephraim Anierobi < > ephraimanier...@gmail.com> wrote: > >> +1 (binding) verified licenses, checksum & signatures >> >>

Re: [VOTE] Release Airflow 2.3.4 from 2.3.4rc1

+1 (binding) On Sat, Aug 20, 2022 at 6:37 PM Jorrick Sleijster wrote: > +1 (non-binding). > > Verified this release (due to #25296) will enable us to deploy Airflow > with our plugin again :) > > Op za 20 aug. 2022 om 16:30 schreef Ash Berlin-Taylor : > >> +1 (binding) >> >> On 20 August 2022 15

Re: [VOTE] Airflow Providers prepared on 2022-09-05

+1 binding On Mon, Sep 5, 2022 at 11:14 PM Jarek Potiuk wrote: > +1 binding > > On Mon, Sep 5, 2022 at 9:40 PM Kaxil Naik wrote: > >> +1 binding >> >> On Mon, 5 Sept 2022 at 16:56, Ash Berlin-Taylor wrote: >> >>> Hey all, >>> >>> I have just cut the new wave Airflow Providers packages. This em

Re: [VOTE] Release Airflow 2.4.0 from 2.4.0rc1

+1 binding The dataset feature is really exciting! On Sat, Sep 17, 2022 at 2:06 AM Vikram Koka wrote: > +1 > > Tested the Data Dependency Management and Data Driven Scheduling (defined > in AIP-48), with Datasets created and configured as dependencies between > DAGs. > Tested the DAG triggering

Re: [VOTE] Release apache-airflow-providers-cncf-kubernetes from 4.4.0rc

+1 binding On Thu, Sep 22, 2022 at 6:42 PM Jarek Potiuk wrote: > +1 (binding) - checked signatures, hashes, licences. It installs cleanly > on Airflow 2.4.0/ > > On Thu, Sep 22, 2022 at 5:32 PM Ash Berlin-Taylor wrote: > >> A slightly unusal one this time (full provider release will happen next

Re: [VOTE] Airflow Providers prepared on September 28, 2022

+1 binding On Fri, Sep 30, 2022 at 12:36 AM Jed Cunningham wrote: > +1 (binding) > > Checked signatures, checksums, and licences. >

Re: Github Issue Triaging

The backlog is actually in good shape. Most of the open issues just need attention from a knowledgeable contributor in the specific area to add some pointers if the issue is valid or not. The protocol for triage can be found in: https://github.com/apache/airflow/blob/main/ISSUE_TRIAGE_PROCESS.rst

Re: Github Issue Triaging

wrote: > >> Hey Elad! >> >> Yupp, I read through that rst and I'm going to help triage incoming >> issues more frequently. Though I do think reviewing the backlog of issues >> every quarter or so can be a useful exercise as well. >> >> Consider this my req

Re: [VOTE] Release Airflow 2.4.2 from 2.4.2rc1

+1 binding checked a few example dags. looks good On Mon, Oct 24, 2022 at 9:10 AM Ephraim Anierobi wrote: > One more binding vote is needed, please. > > Thanks, > -Ephraim > > On 2022/10/20 12:25:26 Ephraim Anierobi wrote: > > Hey fellow Airflowers, > > > > > > I have cut Airflow 2.4.2rc1. This

Re: [VOTE] October 2022 PR of the Month

I think https://github.com/apache/airflow/pull/25717 Add SQLExecuteQueryOperator which was merged this month is a good candidate (sorry missed the #protm tagging) This operator is something we wanted for a really long time (initial PR was in 2020) It took a while to get this done, it involved a lot

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

+1 binding This would be a great improvement! On Thu, Nov 17, 2022 at 7:32 AM Robert Karish wrote: > +1 (non-binding) > > Looks like a great improvement! > > Best, > Robert > > On Thu, Nov 17, 2022 at 12:30 AM Ping Zhang wrote: > >> +1 binding. >> >> Thanks for proposing this work. It will lead

[VOTE] Airflow Providers prepared on December 14, 2022 (RC1)

llowing the below links: https://pypi.org/project/apache-airflow-providers-apache-hive/5.0.0rc1/ https://pypi.org/project/apache-airflow-providers-microsoft-azure/5.0.1rc1/ Cheers, Elad Kalif

Re: [LAZY CONSENSUS] Release of API Clients

Pierre do we have this decision documented in the README so users are 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 proposal is

[RESULT][VOTE] Airflow Providers - release of December 14, 2022 (RC1)

Hello, Apache Airflow Providers (based on RC1) have been accepted. 4 "+1" binding votes received: - Elad Kalif (binding) - Jarek Potiuk (binding) - Jed Cunningham (binding) - Ash Berlin-Taylor (binding) 4 "+1+ non-binding votes received: - Pankaj Koti - Bharanidharan Manimuth

[ANNOUNCE] Airflow Providers released on December 14, 2022 are ready

lling-from-pypi The documentation is available at https://airflow.apache.org/docs/ and linked from the PyPI packages. Cheers, Elad Kalif

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

Hello Airflow Community, I am happy to announce that the Project Management Committee (PMC) for Apache Airflow has invited Niko Oliveira (github nickname o-nikolas) to become a committer and we are pleased to announce that he has accepted. Congratulations Niko, and welcome! Elad on behalf of Air

[VOTE] Airflow Providers prepared on January 02, 2023 - RC2

providers-slack/7.1.1rc2/ https://pypi.org/project/apache-airflow-providers-ssh/3.4.0rc2/ https://pypi.org/project/apache-airflow-providers-telegram/3.1.1rc2/ https://pypi.org/project/apache-airflow-providers-trino/4.3.1rc2/ Cheers,Elad Kalif

[RESULT][VOTE] Airflow Providers - release of January 02, 2023

Hello, Apache Airflow Providers (based on RC2) have been accepted. 4 "+1" binding votes received: - Elad Kalif (binding) - Jed Cunningham (binding) - Jarek Potiuk (binding) - Ephraim Anierobi(binding) 4 "+1+ non-binding votes received: - Pankaj Koti - Phani Kumar - Raja

[ANNOUNCE] Airflow Providers released on Janurary 02, 2023 released

rflow-providers /installing-from-sources You can install the providers via PyPI: https://airflow.apache.org/docs/apache-airflow-providers /installing-from-pypi The documentation is available at https://airflow.apache.org/docs/ and linked from the PyPI packages. Cheers, Elad Kalif

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

+1 (binding) On Mon, Jan 9, 2023 at 7:07 PM Jarek Potiuk wrote: > +1 (binding) > > On Mon, Jan 9, 2023 at 6:01 PM Ferruzzi, Dennis > wrote: > >> +1 non-binding >> >> -- >> *From:* Ash Berlin-Taylor >> *Sent:* Monday, January 9, 2023 8:27 AM >> *To:* dev@airflow.apac

[VOTE] Airflow Providers prepared on January 14, 2023

/https://pypi.org/project/apache-airflow-providers-mysql/4.0.0rc1/https://pypi.org/project/apache-airflow-providers-slack/7.2.0rc1/ Cheers, Elad Kalif

[RESULT][VOTE] Airflow Providers - release of January 14, 2023

Hello, Apache Airflow Providers (based on RC1) have been accepted. Docker provider RC1 is excluded from this release. 3 "+1" binding votes received: - Elad Kalif (binding) - Jarek Potiuk (binding) - Ephraim Anierobi(binding) 6 "+1+ non-binding votes received: - Pankaj Kot

[ANNOUNCE] Airflow Providers released on January 14, 2023 are ready

pache-airflow-providers /installing-from-pypi The documentation is available at https://airflow.apache.org/docs/ and linked from the PyPI packages. Cheers, Elad Kalif

[VOTE] Airflow Providers prepared on January 23, 2023

rflow/issues/29103You can find packages as well as detailed changelog following the below links: https://pypi.org/project/apache-airflow-providers-apache-cassandra/3.1.1rc1/ https://pypi.org/project/apache-airflow-providers-docker/3.5.0rc1/ https://pypi.org/project/apache-airflow-providers-papermill/3.1.1rc1/ Cheers, Elad Kalif

Re: [VOTE] Airflow Providers prepared on January 23, 2023

t in the future whether those two > changes have any real impact, so from a release management perspective > it is cleaner to release it. > > J. > > On Mon, Jan 23, 2023 at 3:01 PM Elad Kalif wrote: > > > > Hey all, > > > > I have just cut ad hoc release for

[RESULT][VOTE] Airflow Providers - release of January 23, 2023

Hello, Apache Airflow Providers (based on RC1) have been accepted. This release include the following providers: docker, apache.cassandra, papermill 3 "+1" binding votes received: - Elad Kalif (binding) - Jarek Potiuk (binding) - Jed Cunningham (binding) 1 "+1+ non-binding

[ANNOUNCE] Airflow Providers prepared on January 23, 2023 are ready

-pypi The documentation is available at https://airflow.apache.org/docs/ and linked from the PyPI packages. Cheers, Elad Kalif

Re: AIP-49 OpenTelemetry Support - Take Three

I know Howard (AIP creator) was looking for developers to assist on this. Howard - Can you share status/progress? On Sat, Jan 28, 2023 at 12:50 AM Ferruzzi, Dennis wrote: > Third time’s the charm? > > Hi folks, looks like AIP-49 [1] hasn’t been touched in a while and I am > interested in getti

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

+1 binding בתאריך יום ד׳, 1 בפבר׳ 2023, 20:47, מאת Ephraim Anierobi ‏< ephraimanier...@gmail.com>: > +1 (binding) > > On Wed, 1 Feb 2023 at 20:35, Pierre Jeambrun > wrote: > >> Hello all, >> >> We need more votes here :) >> >> I would really like to see this move forward as it fixes an important

Re: [DISCUSSION] Move K8S and Celery Executors (and related) to respective providers?

I agree with Jarek. provider release cycle is faster than Airflow core. We can also release ad-hoc specific provider. There is no cherry picking and on top of that with providers we can back port a fix to older versions of Airflow (should we want to) which is something we don't do for core release

Re: [VOTE] Release Apache Airflow Helm Chart 1.8.0 based on 1.8.0rc1

+1 (binding) Since the reports by Jules don't indicate regression I see no reason to block this release. Should release manager decide the bug fixes are important we can prepare a followup 1.8.1 release On Mon, Feb 6, 2023 at 12:23 PM Ephraim Anierobi wrote: > +1 (binding) since the issues ident

[VOTE] Airflow Providers prepared on February 08, 2023

rs-presto/4.2.2rc1/https://pypi.org/project/apache-airflow-providers-sftp/4.2.2rc1/https://pypi.org/project/apache-airflow-providers-snowflake/4.0.3rc1/https://pypi.org/project/apache-airflow-providers-tableau/4.1.0rc1/https://pypi.org/project/apache-airflow-providers-trino/4.3.2rc1/ Cheers, Elad Kalif

[RESULT][VOTE] Airflow Providers - February 08, 2023

Hello, Apache Airflow Providers (based on RC1) have been accepted. 3 "+1" binding votes received: - Elad Kalif (binding) - Jarek Potiuk (binding) - Jed Cunningham (binding) 6 "+1+ non-binding votes received: - Pankaj Koti - Oliveira Niko - Rajath Srinivasaiah - Pankaj Sing

[ANNOUNCE] Airflow Providers prepared on February 08, 2023 are ready

https://airflow.apache.org/docs/ and linked from the PyPI packages. Cheers, Elad Kalif

[Discussion] Set further policies for triaging issues

Hi everyone, It's been a while since we talked about the issue triage process. Currently our process involves a lot of manual work of pinging issue authors and I'm looking to automate some of it. Here are my suggestions: 1. add a new bot automation to detect core bug issues (kind:bug, area:code)

Re: [Discussion] Set further policies for triaging issues

we should have some automation to close the stale issue. >> >> Few questions I have >> - We have currently more than 700 issues and many of them have had no >> activity since a year. What will we do with those issues? >> - Why close only stale issues not stale PR

Re: [Discussion] Set further policies for triaging issues

; some way to incentivise and involve committers to provide feedback to > those > > * The stats could help us to understand if we are falling behind and > maybe we could have some weekly summary of stats that would help us > with understanding if we should do something and up-end our effor

Re: [Discussion] Set further policies for triaging issues

will be closing only issues/PRs which are "pending response". All > the other issues will be either acknowledged by a maintainer and at > least vaguely planned to work on, or converted to a discussion, or > fixed or marked as "good first issue" for anyone to pick up. >

Re: [Discussion] Set further policies for triaging issues

do about issues that have been triaged and the user > "responded" (and no-one will follow up - this happens). Are we going > to track them too or is it something to tackle next ? > > J. > > > > On Mon, Feb 13, 2023 at 10:02 AM Elad Kalif wrote: > > > >

Re: [Discussion] Set further policies for triaging issues

Cool. So it seems like we have an agreement on the concept. lets review the details/specific concerns in the PR https://github.com/apache/airflow/pull/29554 On Mon, Feb 13, 2023 at 12:27 PM Jarek Potiuk wrote: > Fine for me to start this way :) > > On Mon, Feb 13, 2023 at 10:56 AM E

Re: [VOTE] AIP-53 OpenLineage in Airflow

+1 binding On Fri, Feb 17, 2023 at 5:55 PM Jed Cunningham wrote: > +1 binding >

[VOTE] Airflow Providers prepared on February 18, 2023

org/project/apache-airflow-providers-http/4.2.0rc1/ https://pypi.org/project/apache-airflow-providers-microsoft-azure/5.2.1rc1/ https://pypi.org/project/apache-airflow-providers-sftp/4.2.3rc1/ https://pypi.org/project/apache-airflow-providers-snowflake/4.0.4rc1/ Cheers, Elad Kalif

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

+1 (binding) On Tue, Feb 21, 2023 at 8:33 PM Josh Fell wrote: > +1 binding > > On Tue, Feb 21, 2023 at 11:21 AM Jarek Potiuk wrote: > >> And just to add as I missed that in the original mail - this is "code >> modification" vote - so all committers have a binding vote. >> https://www.apache.org

[RESULT][VOTE] Airflow Providers - February 18, 2023

Hello, Apache Airflow Providers (based on RC1) have been accepted. 3 "+1" binding votes received: - Elad Kalif (binding) - Jarek Potiuk (binding) - Ash Berlin-Taylor (binding) 5 "+1+ non-binding votes received: - Rajath Srinivasaiah - Phani Kumar - Pankaj Koti - Josh Fell - Pan

[ANNOUNCE] Airflow Providers prepared on February 18, 2023 are ready

/docs/ and linked from the PyPI packages. Cheers, Elad Kalif

Re: Apache Airflow Newsletter | February 2023

CVEs are announced on users mailing list (not dev) as the action about the CVE is relevant to the users of Airflow not to the developers of Airflow. Example: https://lists.apache.org/thread/zdr8ovfttbh7kj0lydgcw88tbt2nmkcy We also announce them on Slack #anno

[VOTE] Airflow Providers prepared on March 03, 2023

-providers-sftp/4.2.4rc1/ https://pypi.org/project/apache-airflow-providers-ssh/3.5.0rc1/ https://pypi.org/project/apache-airflow-providers-telegram/4.0.0rc1/ https://pypi.org/project/apache-airflow-providers-yandex/3.3.0rc1/ <https://pypi.org/project/apache-airflow-providers-snowflake/4.0.4rc1/> Cheers, Elad Kalif

Re: [LAZY CONSENSUS] Unsubscribe links in users@ mailing list footers

+1 On Fri, Mar 3, 2023 at 4:42 PM Ferruzzi, Dennis wrote: > +1 always a good idea > > > -- > *From:* Jarek Potiuk > *Sent:* Thursday, March 2, 2023 11:24 PM > *To:* dev@airflow.apache.org > *Subject:* [EXTERNAL] [LAZY CONSENSUS] Unsubscribe links in users@ > mailing

Re: [VOTE] Airflow Providers prepared on March 03, 2023

Voting is now closed. Bug was found in the hasicrop provider thus will cut RC2 for that provider. On Mon, Mar 6, 2023 at 5:09 PM Josh Fell wrote: > +1 (non-binding) > > Verified a few bug fixes across providers. > > On Mon, Mar 6, 2023 at 8:56 AM Jed Cunningham > wrote: > >> +1 (binding) >> >>

[RESULT][VOTE] Airflow Providers - March 03, 2023

Hello, Apache Airflow Providers (based on RC1) have been accepted. Note: Hashicorp provider is excluded from this release. RC2 will be cut shortly. 3 "+1" binding votes received: - Elad Kalif (binding) - Jarek Potiuk (binding) - Jed Cunningham (binding) 4 "+1+ non-binding

[ANNOUNCE] Airflow Providers prepared on March 03, 2023 are ready

-from-sources You can install the providers via PyPI: https://airflow.apache.org/docs/apache-airflow-providers /installing-from-pypi The documentation is available at https://airflow.apache.org/docs/ and linked from the PyPI packages. Cheers, Elad Kalif

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

Did we have a lazy consensus for this policy? I can't find the thread. Wanted to see if I can apply the policy on hashicorp provider 3.3.0rc2 but since I can't find the policy thread I'll go with the 72 hours window. On Wed, Nov 30, 2022 at 11:59 PM Jed Cunningham wrote: > +1 to shorter follow u

[VOTE] Airflow Providers prepared on March 07, 2023

m/apache/airflow/issues/29948You can find packages as well as detailed changelog following the below links: https://pypi.org/project/apache-airflow-providers-hashicorp/3.3.0rc2/ Cheers, Elad Kalif

[RESULT][VOTE] Airflow Providers - March 07, 2023

Hello, Apache Airflow Providers (based on RC2) have been accepted. 3 "+1" binding votes received: - Elad Kalif (binding) - Kaxil Naik (binding) - Jarek Potiuk (binding) 2 "+1+ non-binding votes received: - Hussein Awala - Niko Oliveira Vote thread: https://lists.ap

[ANNOUNCE] Airflow Providers prepared on March 07, 2023 are released

pache-airflow-providers/installing-from-sources You can install the providers via PyPI: https://airflow.apache.org/docs/apache-airflow-providers/installing-from-pypi The documentation is available at https://airflow.apache.org/docs/ and linked from the PyPI packages. Cheers, Elad Kalif

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

Added reference for this thread in relevant release docs https://github.com/apache/airflow/pull/30037 On Fri, Mar 10, 2023 at 10:12 PM Pierre Jeambrun wrote: > 72 hours have passed, we will start using this policy for our future > releases. > > Thanks > > Le mar. 7 mars 2023 à 21:29, Ferruzzi, D

Re: [VOTE] Release Airflow 2.5.2 from 2.5.2rc1

+1 (binding) checked some test dags looks good! On Sat, Mar 11, 2023 at 11:26 PM Pierre Jeambrun wrote: > 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 (bindi

Re: [VOTE] Release Airflow 2.5.2 from 2.5.2rc2

+1 binding On Tue, Mar 14, 2023 at 9:51 AM Phani Kumar wrote: > +1 non-binding > > On Tue, Mar 14, 2023 at 1:14 PM Ephraim Anierobi < > ephraimanier...@gmail.com> > wrote: > > > +1 binding > > > > On Tue, 14 Mar 2023 at 08:36, Jarek Potiuk wrote: > > > > > +1 (binding) checked signatures, check

Re: [ANNOUNCE] New PMC member: Pierre Jeambrun

Congrats! well deserved! On Thu, Mar 16, 2023 at 9:03 AM Ephraim Anierobi wrote: > Congratulations Pierre! Well deserved! > > On Thu, 16 Mar 2023 at 08:00, Pierre Jeambrun > wrote: > > > Thank you for your cheerful messages. > > > > Looking forward to more contributions with all of you. > > > >

Re: [ANNOUNCE] New PMC member: Brent Bovenzi

Congrats! well deserved! On Thu, Mar 16, 2023 at 9:03 AM Ephraim Anierobi wrote: > Congratulations Brent! Well deserved! > > On Thu, 16 Mar 2023 at 06:11, Vikram Koka > wrote: > > > Awesome! Congratulations Brent, well deserved! > > > > > > On Wed, Mar 15, 2023 at 12:10 PM Pierre Jeambrun > >

Re: [DISCUSS] a cache for Airflow Variables

To me Airflow is not "open and play". It is not a closed system that guides you how to develop. Workflow as code requires more skills. There are stuff to learn before authoring dags. This discussion is about Variables but I might ask similar question about users who query API as part of top level c

Re: [DISCUSS] a cache for Airflow Variables

Jarek I can argue that by doing that the problem is not gone but just reduced to a level where it's even harder to spot and adresses by the users. This is the worst kind of problems to tackle! In my prespective if we don't address the issue directly (general solution to top level code issues) any

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

I like to raise a (minor?) point about the new trigger rule (see https://github.com/apache/airflow/pull/30270 ) which was not part of the original design (at least not explicitly?) which has some drawbacks that we need to be mindful about: 1. The trigger rule class is public API. Adding an inte

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

Thanks Daniel, Let me clarify my concern. When user set setup/teardown he has no idea unique trigger rule is set under the hood. The user also has no idea that trigger rules are even involved. That is not something he sees unless he checks the code of teardown and setup decorators. This means tha

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

Thank you everyone. My concerns have been addressed. I still think we should somehow advise users not to use this new trigger rule explicitly but that is something we can talk in the PR itself. בתאריך יום ג׳, 28 במרץ 2023, 09:17, מאת Jarek Potiuk ‏: > Maybe just `NukeOperator` simply :) > > On Tu

Re: [DISCUSS] Exclude some providers that hold us back from releasing

I agree that we should exclude providers that block us. On Tue, Mar 28, 2023 at 9:58 PM Ferruzzi, Dennis wrote: > I don't have any issue with this in general, in fact I think it's not a > bad idea to trim out older unused/unmaintained providers. But what are the > criteria for marking a provid

Re: [DISCUSS] Exclude some providers that hold us back from releasing

- so actually > > a "suspension" that can be "resumed". We are not going to remove the > > code (for now at least but we might have some criteria for that in the > > future) - so bringing a change which fixes it (usually by a dependenc

Re: [VOTE] Release Airflow 2.5.3 from 2.5.3rc2

+1 binding tested some of my demo dags. looks good. On Thu, Mar 30, 2023 at 7:31 PM Jarek Potiuk wrote: > +1 (binding) - checked my issues, tested it a bit, verified licences, > signatures checksums - all looks good! > > On Thu, Mar 30, 2023 at 6:09 PM Brent Bovenzi > wrote: > > > > +1 binding

[VOTE] Airflow Providers prepared on April 02, 2023

/3.2.1rc1/ https://pypi.org/project/apache-airflow-providers-microsoft-azure/5.3.0rc1/ https://pypi.org/project/apache-airflow-providers-smtp/1.0.0rc1/ https://pypi.org/project/apache-airflow-providers-ssh/3.6.0rc1/ Cheers, Elad Kalif

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

gt; Just to https://github.com/apache/airflow/issues/30427 > > > > > > (link got accidentally garbled) :) > > > > > > On Sun, Apr 2, 2023 at 8:58 AM Elad Kalif wrote: > > > > > >> Hey all,I have just cut the new wave Airflow Providers pack

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

red on April 02, 2023 > > +1 (non-binding) > > On Mon, Apr 3, 2023 at 2:42 AM Elad Kalif wrote: > > > Hi Phani, > > no this is not yet merged. Once merged it will be released in the > followup > > provider release. > > > > On Mon, Apr 3, 2023 at 6:36

[RESULT][VOTE] Airflow Providers - April 02, 2023

Hello, Apache Airflow Providers (based on RC1) have been accepted. 3 "+1" binding votes received: - Elad Kalif (binding) - Jarek Potiuk (binding) - Pierre Jeambrun (binding) 7 "+1+ non-binding votes received: - Phani Kumar - Josh Fell - Hussein Awala - Pankaj Koti - Phani

[ANNOUNCE] Airflow Providers prepared on April 02, 2023 are ready

/docs/apache-airflow-providers/installing-from-sources You can install the providers via PyPI: https://airflow.apache.org/docs/apache-airflow-providers/installing-from-pypi The documentation is available at https://airflow.apache.org/docs/ and linked from the PyPI packages. Cheers, Elad Kalif

[VOTE] Airflow Providers prepared on April 09, 2023

/9.0.0rc1/ https://pypi.org/project/apache-airflow-providers-microsoft-azure/5.3.1rc1/ https://pypi.org/project/apache-airflow-providers-smtp/1.0.1rc1/ Cheers, Elad Kalif

[RESULT][VOTE] Airflow Providers - April 09, 2023

Hello, Apache Airflow Providers (based on RC1) have been accepted. The following providers: - google - microsoft.azure are excluded from this release and RC2 will be cut for them shortly. 4 "+1" binding votes received: - Elad Kalif (binding) - Jarek Potiuk (binding) - Jed

[ANNOUNCE] Airflow Providers prepared on April 09, 2023 are released

The documentation is available at https://airflow.apache.org/docs/ and linked from the PyPI packages. Cheers, Elad Kalif

[VOTE] Airflow Providers prepared on April 12, 2023

oviders-google/9.0.0rc2 https://pypi.org/project/apache-airflow-providers-microsoft-azure/5.3.1rc2/ Cheers,Elad Kalif

[RESULT][VOTE] Airflow Providers - April 12, 2023

Hello, Apache Airflow Providers (based on RC2) have been accepted. 3 "+1" binding votes received: - Elad Kalif (binding) - Jarek Potiuk (binding) - Ephraim Anierobi (binding) 1 "+1" non-binding votes received: - Hussein Awala Vote thread: https://lis

[ANNOUNCE] Airflow Providers prepared on April 12, 2023 are released

e.org/docs/ and linked from the PyPI packages. Cheers, Elad Kalif

[VOTE] Airflow Providers prepared on April 21, 2023

roject/apache-airflow-providers-snowflake/4.0.5rc1/ https://pypi.org/project/apache-airflow-providers-sqlite/3.3.2rc1/ https://pypi.org/project/apache-airflow-providers-trino/5.0.0rc1/ Cheers, Elad Kalif

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

Vote is now closed. based on feedback from issue testing https://github.com/apache/airflow/issues/30803 amazon: 8.0.0rc1 is excluded from this release. I will cut rc2 for amazon provider On Mon, Apr 24, 2023 at 9:45 PM Pankaj Singh wrote: > +1 non binding > > our astronomer-providers and astro

[RESULT][VOTE] Airflow Providers - April 21, 2023

Hello, Apache Airflow Providers (based on RC1) have been accepted. Amazon provider is excluded from this release and RC2 will follow. 3 "+1" binding votes received: - Elad Kalif (binding) - Jarek Potiuk (binding) - Jed Cunningham (binding) 5 "+1" non-binding votes recei

[ANNOUNCE] Airflow Providers prepared on April 21, 2023 are released

https://airflow.apache.org/docs/apache-airflow-providers/installing-from-pypi The documentation is available at https://airflow.apache.org/docs/ and linked from the PyPI packages. Cheers, Elad Kalif

[VOTE] Airflow Providers prepared on April 25, 2023

ame the artifact without modifyingthe artifact checksums when we actually release.The status of testing the providers by the community is kept here: https://github.com/apache/airflow/issues/30849 You can find packages as well as detailed changelog following the below links: https://pypi.org/projec

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

This vote is cancelled. RC3 will follow On Wed, Apr 26, 2023 at 4:23 AM Mehta, Shubham wrote: > Thank Jarek, good catch! You're right, it's better to keep aiobotocore as > additional dependency for now. > If you attempt to install apache-airflow-providers-amazon[aiobotocore] > using constraints

[VOTE] Airflow Providers prepared on April 26, 2023

ame the artifact without modifyingthe artifact checksums when we actually release.The status of testing the providers by the community is kept here: https://github.com/apache/airflow/issues/30880 You can find packages as well as detailed changelog following the below links: https://pypi.org/projec

[RESULT][VOTE] Airflow Providers - April 26, 2023

Hello, Apache Airflow Providers (based on RC3) have been accepted. 3 "+1" binding votes received: - Elad Kalif (binding) - Jarek Potiuk (binding) - Ephraim Anierobi (binding) 3 "+1" non-binding votes received: - Hussein Awala - Pankaj Singh - Phani Kumar Vote thread: http

[ANNOUNCE] Airflow Providers prepared on April 26, 2023 are released

pache-airflow-providers/installing-from-sources You can install the providers via PyPI: https://airflow.apache.org/docs/apache-airflow-providers/installing-from-pypi The documentation is available at https://airflow.apache.org/docs/ and linked from the PyPI packages. Cheers, Elad Kalif

Re: [VOTE] Release Airflow 2.6.0 from 2.6.0rc4

+1 (binding) ran dags locally works great On Fri, Apr 28, 2023 at 5:13 PM Jarek Potiuk wrote: > +1 (binding) - checked signatures, checksums, licences. Installed and > tested it locally for a number of cases. Looks good! > > On Fri, Apr 28, 2023 at 1:00 PM Ephraim Anierobi < > ephraimanier...@ap

Re: [VOTE] Release Airflow 2.6.0 from 2.6.0rc5

+1 binding בתאריך שבת, 29 באפר׳ 2023, 21:08, מאת Pierre Jeambrun ‏< pierrejb...@gmail.com>: > +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

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

+1 binding On Tue, May 9, 2023 at 10:42 AM Jarek Potiuk wrote: > +1 (binding) - all looks good and docs are updated, checked signatures, > checksums licences, run some basic tests with the final results > > > On 2023/05/07 16:50:42 Ephraim Anierobi wrote: > > Hey fellow Airflowers, > > > > I hav

Re: [VOTE] Release Airflow 2.6.1 from 2.6.1rc3

+1 binding tested example dags. looks good. On Mon, May 15, 2023 at 9:32 PM Pankaj Singh wrote: > +1 (non-binding) > > On Mon, May 15, 2023 at 11:49 PM Pankaj Koti > wrote: > > > +1 (non-binding) > > > > I tested our example DAGs for asynchronous providers kept in > > astronomer-providers on t

[VOTE] Airflow Providers prepared on May 16, 2023

providers-trino/5.1.0rc1/ https://pypi.org/project/apache-airflow-providers-vertica/3.4.0rc1/ https://pypi.org/project/apache-airflow-providers-zendesk/4.3.0rc1/ Cheers,Elad Kalif

Re: [VOTE] Airflow Providers prepared on May 16, 2023

andler import > S3TaskHandler > >> File > >> > "/usr/local/lib/python3.10/site-packages/airflow/providers/amazon/__init__.py", > >> line 35, in > >> if packaging.version.parse(airflow.version.version) < > >> packaging.version.

[VOTE] Airflow Providers prepared on May 19, 2023

providers-trino/5.1.0rc2/ https://pypi.org/project/apache-airflow-providers-vertica/3.4.0rc2/ https://pypi.org/project/apache-airflow-providers-zendesk/4.3.0rc2/ Cheers,Elad Kalif

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

+1 (binding) On Mon, May 22, 2023 at 7:50 AM Pankaj Singh wrote: > + 1 (non-binding) > > verify the newly generated pool model. > > Yes, as mentioned by Pierre Jeambrun there is > apache-airflow-client-2.6.0-source archive inside 2.6.1 source. It would be > great if we can clean it. > > On Mon,

  1   2   3   4   5   6   >