potiuk commented on issue #11879: URL: https://github.com/apache/airflow/issues/11879#issuecomment-724097929
Hello everyone, I prepared the first version of the documentation update including Provider Packages and it's dependencies. It addresses (I hope) the questions pointed out by Vikram and Pete, I invite everyone interested in the discussion in the PR: https://github.com/apache/airflow/pull/12203 Suggestions on re-wording are most appreciated, I am not a native speaker, so grammar, wording etc. are equally welcome as a concrete proposal on what to include, what questions/answers to provide, also I look forward to phrase it in a way that will be nice and helpful, and at the same time, it will leave enough freedom and enough information for the customers using Airflow to make their own decisions on how they are testing and validating any upgrades/downgrades. I think we should stress (and this is what I tried to show in the PR) that Provider Packages provide the nice feature that each business /user can incrementally update those providers as they wish, where we as community aim to provide backwards compatibility based on the SemVer versioning principles. We are not able to tell our users how they are going to upgrade, but we can tell them what freedom they have. If you think that - as a community - we should approach it differently - happy to discuss it in the PR and any proposals there are welcome. J. On Mon, Nov 9, 2020 at 11:34 AM Jarek Potiuk <[email protected]> wrote: > Cool. I will try to prepare small "starting point" description PR that > might be a good starting point that we will iterate over during betas. > > On Mon, Nov 9, 2020 at 5:08 AM Pete DeJoy <[email protected]> > wrote: > >> One thing I'd add is the inverse of the second question that @vikramkoka >> <https://github.com/vikramkoka> posed above- if I'd like to upgrade >> Airflow, how can I validate that the provider I'm installing will not >> break? What does that experience look like both from the user perspective >> and from the builder/maintainer perspective? >> >> — >> You are receiving this because you were mentioned. >> Reply to this email directly, view it on GitHub >> <https://github.com/apache/airflow/issues/11879#issuecomment-723742005>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AAERMI23GJAXZLDG6NVYUJTSO5TMJANCNFSM4TAP2IUA> >> . >> > > > -- > > Jarek Potiuk > Polidea <https://www.polidea.com/> | Principal Software Engineer > > M: +48 660 796 129 <+48660796129> > [image: Polidea] <https://www.polidea.com/> > > -- Jarek Potiuk Polidea <https://www.polidea.com/> | Principal Software Engineer M: +48 660 796 129 <+48660796129> [image: Polidea] <https://www.polidea.com/> ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
