How do you propose to address this Ash (and _we_ especially) ? Any idea how
_we_ can do it?
J.
On Tue, Feb 18, 2020 at 10:54 PM Ash Berlin-Taylor wrote:
> -1 from me.
>
> I would favour individual small releases, not a back-port big blob.
> And I would also rather _we_ put the effort in to work
-1 from me.
I would favour individual small releases, not a back-port big blob.
And I would also rather _we_ put the effort in to working out compatibility
issues/breaking changes in providers (and to be honest avoiding them in most
cases) rather than making our users do this guess/experience br
+1
CalVer is a fantasstic idea.
https://calver.org/
On Tue, Feb 18, 2020 at 10:37 PM Jarek Potiuk wrote:
>
> Since we are close to run tests for backport packages at GCP I would like
> to start vote on the release process for backport packages.
>
> The vote will last till Friday, 21st of Feb, 1
Since we are close to run tests for backport packages at GCP I would like
to start vote on the release process for backport packages.
The vote will last till Friday, 21st of Feb, 11pm CET.
The proposal is to release one single backport "providers" package for now
with Calver scheme:
*apache-airfl
I think maybe we should simply gather some evidence on what users are using
the extensions for. I can put together some evidence from my customers, and
maybe others could contribute theirs?
Do others have experience with similar case where people extend Airflow by
modifying Airflow's source code?
I think the kinds of plugins you are talking make sense in some contexts
(e.g. custom views when clicking on a task in the UI, e.g. ability to
visualize the data an ETL job provides) but we should be careful allowing
extensions to more core parts, it will become very hard to change/maintain
the pro
I believe this is one of the cases where we can just go with the consensus
indeed :).
J.
On Tue, Feb 18, 2020 at 12:51 PM Ash Berlin-Taylor wrote:
> Do we need to have a vote on it? I'm mostly interested in answering the
> question about vote in general terms rather than this specific case)
>
>
I have another discussion to start. We've recently talked to a number of
customers who are extending airflow. It's often the case that people are
modifying airflow's source code and later have a hard time with updating it
when newer versions of Airflow are released.
This is a common trait - we've
Do we need to have a vote on it? I'm mostly interested in answering the
question about vote in general terms rather than this specific case)
What do we need votes on, and when is "yeah no one complained, let's do it"
enough?
For example if someone had created a PR for this and had appropriate
All right. I turn it into vote then :)
On Tue, Feb 18, 2020 at 7:45 AM Driesprong, Fokko
wrote:
> I don't have any objection, however, this isn't a [VOTE] right? ;)
>
> Op di 18 feb. 2020 om 00:08 schreef Jarek Potiuk >:
>
> > I see that it's quite welcome change, so I think if no-one else obj
10 matches
Mail list logo
