Re: [VOTE] Airflow Providers prepared on February 12, 2024

-1 (non-binding) for amazon: 8.18.0rc1, cncf.kubernetes: 8.0.0rc1, common.sql: 1.11.0rc2. * Amazon: https://github.com/apache/airflow/pull/36685 doesn’t work as expected in the RC. It holds the DAG in the deferred state forever. * Kubernetes: issue mentioned in

Re: [VOTE] Airflow Providers prepared on February 12, 2024

- 0 (non binding) due to https://github.com/apache/airflow/pull/37279 for the CNCF provider +1 (non binding) for the rest On Tue, Feb 13, 2024 at 5:34 AM Jarek Potiuk wrote: > +1 (binding), checked signatures, checksums, licences, reproducibility. > Checked all my changes are present in the

Re: [VOTE] Airflow Providers prepared on February 12, 2024

+1 (binding), checked signatures, checksums, licences, reproducibility. Checked all my changes are present in the packages. -1 (common.sql missing more-itertools dependency - already merged in main). On Mon, Feb 12, 2024 at 9:13 PM Hussein Awala wrote: > I checked the source code, the

Re: [VOTE] Airflow Providers prepared on February 12, 2024

I checked the source code, the licences, the signatures, and the checksums and tested my changes; all look good. -0 (binding) for cncf.kubernetes provider; #37279 is too risky and needs some testing, I will try to find some time to test all the cases

[LAZY CONSENSUS] Rename slack channels

Hey here, Following the earlier discussion, I am calling for a lazy consensus on renaming of our slack channels: #development -> *#contributors* #first-pr-support -> *#new-contributors* #troubleshooting -> *#user-troubleshooting* #random -> *#random* (hehe) The current #development channel will

Re: [DISCUSS] Rename channels on slack

Ok. Let me then start LAZY CONSENSUS :) On Mon, Feb 12, 2024 at 8:31 PM Aritra Basu wrote: > +1 the names sound good to me as well > > -- > Regards, > Aritra Basu > > On Tue, Feb 13, 2024, 12:45 AM Vincent Beck wrote: > > > +1 > > > > On 2024/02/12 19:12:05 Briana Okyere wrote: > > > Same, +1

Re: [DISCUSS] Rename channels on slack

+1 the names sound good to me as well -- Regards, Aritra Basu On Tue, Feb 13, 2024, 12:45 AM Vincent Beck wrote: > +1 > > On 2024/02/12 19:12:05 Briana Okyere wrote: > > Same, +1 > > > > On Mon, Feb 12, 2024 at 9:15 AM Oliveira, Niko > > > wrote: > > > > > I'm happy with that set of names +1

Re: [DISCUSS] Rename channels on slack

+1 On 2024/02/12 19:12:05 Briana Okyere wrote: > Same, +1 > > On Mon, Feb 12, 2024 at 9:15 AM Oliveira, Niko > wrote: > > > I'm happy with that set of names +1 > > > > > > From: Jarek Potiuk > > Sent: Monday, February 12, 2024 3:37:35 AM > > To:

Re: [DISCUSS] Rename channels on slack

Same, +1 On Mon, Feb 12, 2024 at 9:15 AM Oliveira, Niko wrote: > I'm happy with that set of names +1 > > > From: Jarek Potiuk > Sent: Monday, February 12, 2024 3:37:35 AM > To: dev@airflow.apache.org > Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] Rename

Re: [DISCUSS] Rename channels on slack

I'm happy with that set of names +1 From: Jarek Potiuk Sent: Monday, February 12, 2024 3:37:35 AM To: dev@airflow.apache.org Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] Rename channels on slack CAUTION: This email originated from outside of the

Re: [DISCUSS] Rename channels on slack

Yeah. Precisely I think the persona is the key problem - similarly to the recent change in our community page https://airflow.apache.org/community/ where we split "Want to contribute?" and "Are you a user?" (and an observation that #development is in "user" section does not make it clearer). So

[VOTE] Airflow Providers prepared on February 12, 2024

Hey all, I have just cut the new wave Airflow Providers packages. This email is calling a vote on the release, which will last for 72 hours - which means that it will end on February 15, 2024 11:30 AM UTC and until 3 binding +1 votes have been received. Consider this my (binding) +1. Airflow

Re: [DISCUSS] Rename channels on slack

The challenge is the persona here. I bet people think that they are doing "dev" on Airflow when writing dags :-). On Fri, 9 Feb 2024 at 20:17, Briana Okyere wrote: > Love this thread. From my experience in community management (for whatever > it's worth), naming channels after personas is the