Yeah. I think we need to fight a bit with the perception of "stick with the version you have" as well. There are some people who are still using Airflow 2.0.0 while we are at 2.1.2 already..
And while it comes from 1.10.* past where sometimes there were breaking changes between patch-level versions, it makes no sense to continue this now when we adopted and strictly follow SemVer, and Airflow 2 changing to 3 should be the only "important" factor that should keep people from pretty much immediate upgrade. Human habits are very difficult to change and we need to make a deliberate (and extra) effort to change it. J. On Wed, Jul 21, 2021 at 8:49 PM Leah Cole <[email protected]> wrote: > I've used both Airflow 2 and Airflow 2.0+ in presentations to be all > encompassing - but yeah, we should all probably make note of any > presentations we're giving/material we're making going forward to make sure > we're not creating a maintenance nightmare by ONLY saying 2.0 :) > > On Sun, Jul 18, 2021 at 10:09 AM Jarek Potiuk <[email protected]> wrote: > >> Hey everyone, >> >> During the summit I realized one thing. For such a long time we stuck >> with "Airflow 2.0 is coming" that it became almost automated (well, for me >> at least) to add the ".zero". Similar to "master" -> "main" it needs some >> deliberate effort to break with the habit. And I found that "2.0" became a >> bit too sticky for me in both writing and speaking. >> >> I kept on correcting myself to "Airflow 2" all the time (and I think - >> but I am not 100% sure of that) I've heard 2.0 every now and then from >> others. >> >> Is it just me ? Or should we all unlearn "Airflow 2.0" and switch to >> "Airflow 2" :) ? >> >> I think we should all pay attention to it :). >> >> J. >> >> -- >> +48 660 796 129 <+48%20660%20796%20129> >> > > > -- > > Leah Cole (she/her) | Developer Programs Engineer | [email protected] | +1 > (925) 257-2112 > *I'm working weird hours during this pandemic and am sometimes a bit > slower to respond to PRs/CLs than normal. Please feel free to send me a > gentle ping for a status update if my slowness is blocking you and I'll do > my best to give you an ETA. * > > -- +48 660 796 129
