For what I'm looking for out of a 2.0, as an operator/cluster admin
(separate from what I'd like to see as a DAG developer), I'd love to see:
- Combine breaking changes into 2.0, and do as few as possible after
- A semver policy for 2.0 and onwards. (For instance we got bit hard by a
breaking API
All those are very important and we are going to work on some of them as
well.
I think if there are breaking changes, we should rather try to fit them in
2.0 release - at least to the point that they can be base for extending it
in later versions in backwards-compatible way (maybe then we should a
Great designs! I had no time to comment on it before but I really like
where it goes.
I think Roadmap is an important one and it should be at the top-level.
Projects like flink for example have it at the top level. But we have to
make sure to keep it always updated :).
J.
On Wed, Sep 25, 2019 at
Fantastic! I am waiting for your presentation.
On Mon, Sep 30, 2019 at 1:34 PM Tomasz Urbaszek
wrote:
>
> Hi,
>
> I would like to give a talk about scaffolding tool we use for generating
> GCP operators code. Where should I send more information?
>
> Best wishes,
> Tomek
>
>
> On Wed, Sep 25, 20
Hi,
I would like to give a talk about scaffolding tool we use for generating
GCP operators code. Where should I send more information?
Best wishes,
Tomek
On Wed, Sep 25, 2019 at 9:08 AM Driesprong, Fokko
wrote:
> Awesome!
>
> I took the liberty of adding the meetup to the list:
> https://cwik
