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

2022-11-15 Thread Jeambrun Pierre
+1 (binding) On Wed 16 Nov 2022 at 03:20, Jarek Potiuk wrote: > +1 (binding) > > > On Tue, Nov 15, 2022 at 10:07 PM Oliveira, Niko > wrote: > > > > Hey folks! > > > > I would like to start a vote for "AIP-51 - Removing Executor Coupling > from Core Airlfow". > > > > You can find the AIP here:

Re: [DISCUSSION] Release of API clients

2022-11-15 Thread Sumit Maheshwari
> > Not with every release. I am talking about releasing it with every release > "if it is needed". > That clarifies, plz go ahead. On Tue, Nov 15, 2022 at 5:15 PM Jarek Potiuk wrote: > And just to add one "clarifying" condition here: > > If we release Airflow 2.X.0 (the first release in the

Re: [Discussion] Airflow Newsletter name and branding

2022-11-15 Thread Pankaj Singh
+1 for Atmosphere On Tue, Nov 15, 2022 at 11:29 PM Tomasz Urbaszek wrote: > Atmosphere +1! > > T. > -- Pankaj Singh Software Engineer, Astronomer Inc | https://www.linkedin.com/in/pankajiam/

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

2022-11-15 Thread Jarek Potiuk
+1 (binding) On Tue, Nov 15, 2022 at 10:07 PM Oliveira, Niko wrote: > > Hey folks! > > I would like to start a vote for "AIP-51 - Removing Executor Coupling from > Core Airlfow". > > You can find the AIP here: >

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

2022-11-15 Thread Oliveira, Niko
Hey folks! I would like to start a vote for "AIP-51 - Removing Executor Coupling from Core Airlfow". You can find the AIP here: https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-51+Removing+Executor+Coupling+from+Core+Airlfow Discussion threads:

Re: [Discussion] Airflow Newsletter name and branding

2022-11-15 Thread Tomasz Urbaszek
Atmosphere +1! T.

Re: [Discussion] Airflow Newsletter name and branding

2022-11-15 Thread Jeambrun Pierre
+1 for "Asmosphere", like it a lot. Le mar. 15 nov. 2022 à 11:56, Pankaj Koti a écrit : > +1 to "Atmosphere" > Regards, > > > > Pankaj Koti > > *Senior Software Engineer, *OSS Engineering Team. > Location: Pune, India > > Timezone: Indian Standard Time (IST) > > Email: pankaj.k...@astronomer.io

Re: [DISCUSSION] Release of API clients

2022-11-15 Thread Jarek Potiuk
And just to add one "clarifying" condition here: If we release Airflow 2.X.0 (the first release in the MINOR version, the answer to "Do we need to release API Client ?" is always "YES". J. On Tue, Nov 15, 2022 at 12:41 PM Jarek Potiuk wrote: > > > we are talking about the same thing & on

Re: [DISCUSSION] Release of API clients

2022-11-15 Thread Jarek Potiuk
> we are talking about the same thing & on the same page with versioning, > though releasing clients with each Airflow release confuses me. Not with every release. I am talking about releasing it with every release "if it is needed". I do not see anything confusing here. The logic is simple: *

Re: [DISCUSSION] Release of API clients

2022-11-15 Thread Sumit Maheshwari
@Jarek Potiuk we are talking about the same thing & on the same page with versioning, though releasing clients with each Airflow release confuses me. On Tue, Nov 15, 2022 at 4:04 PM Jarek Potiuk wrote: > > > > There had been a discussion around this earlier, though I couldn't find > the

Re: CVE-2022-27949: Apache Airflow: sensitive values in rendered template

2022-11-15 Thread Jarek Potiuk
Additional info: Credit: Apache Airflow PMC would like to thank James Srinivasan for reporting it. On Mon, Nov 14, 2022 at 12:50 AM Jarek Potiuk wrote: > > Severity: low > > Description: > > A vulnerability in UI of Apache Airflow allows an attacker to view unmasked > secrets in rendered

Re: [Discussion] Airflow Newsletter name and branding

2022-11-15 Thread Pankaj Koti
+1 to "Atmosphere" Regards, Pankaj Koti *Senior Software Engineer, *OSS Engineering Team. Location: Pune, India Timezone: Indian Standard Time (IST) Email: pankaj.k...@astronomer.io Mobile: +91 9730079985 On Tue, Nov 15, 2022 at 2:02 AM Jarek Potiuk wrote: > Love the "Atmosphere" name

Re: [DISCUSSION] Release of API clients

2022-11-15 Thread Jarek Potiuk
> > There had been a discussion around this earlier, though I couldn't find the > thread. So if we want to release clients with each Airflow release, then > we've to move away from current semantic versioning, something which we had > decided in that thread. Why ? I think we do not have to do