I think that many times, you only bring things to list after they reach a
certain level of maturity. Sometimes on slack etc you are just working out
how you feel about something, trying to understand something. I think it
is perfectly fine to have such conversations on slack.
Perhaps you find th
BUT LET ME ADD
Can anyone sort of try to focus the discussion here a bit?
Is there anything specific being proposed?
On Wed, Mar 26, 2025 at 9:58 AM Daniel Standish <
daniel.stand...@astronomer.io> wrote:
> I think that many times, you only bring things to list after they reach a
> certain leve
+1 (binding) - Checked SVN, Check in Docker, Reproducible package build,
Licenses, Signatures
On 26.03.25 14:04, Elad Kalif wrote:
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 wi
Hi everyone,
Here is a quick reminder that we have our Airflow 3 dev call tomorrow
Thursday, the 27th of March at 9AM PST (12 pm EST | 4 pm UTC / GMT).
The agenda is pretty short and I expect this to be a quick call.
Proposed agenda:
1. Check in on action items from the last call
- Cleanup of Ai
-1 for Amazon providers. We're still waiting for a few fixes to deploy (ETA
3/31) that if not present will cause an outage for SageMaker Unified Studio
Workflows if this release candidate is deployed. We'd like to exclude from this
release, or possibly delay it until Tuesday next week.
Thanks,
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 March 29,
2025 13:00 PM UTC and until 3 binding +1 votes have been received.
Consider this my (binding) +1.
Airflow Provi
