Jarek, Thanks for bringing this up and vehemently agreed on the need for this.
Elad, great start with the PR. I think we can all add comments to the PR and get it published as soon as possible. On Wed, May 19, 2021 at 2:50 AM Kaxil Naik <[email protected]> wrote: > Nice, I think the PR is a good start, we should also add it docs in > installation.rst or a new page which is linked by installation.rst > > Regards, > Kaxil > > On Wed, May 19, 2021, 10:31 Elad Kalif <[email protected]> wrote: > >> I agree. We should make the version life cycle more noticeable. >> started https://github.com/apache/airflow/pull/15936 as a possible first >> step >> >> On Wed, May 19, 2021 at 10:49 AM Xiaodong Deng <[email protected]> wrote: >> >>> Thanks, Jarek, for bringing up this. >>> >>> I do agree this is very important, and quite many users may be surprised >>> by this even though the timeline has been decided & announced quite a long >>> time ago. >>> >>> Yep, let's make this information more explicit. Among what you have >>> nicely listed, the following two may be good starting point: >>> - banner on our website & GitHub README >>> - campaign through Social Media (maybe our Airflow official twitter >>> account can rolle out a post then folks try to retweet? For LinkedIn, I >>> don't think we have an official account, but everyone can post to their own >>> network) >>> >>> Given it's just ~1 month to go, I suggest we prioritize this a little >>> bit. >>> >>> >>> XD >>> >>> On Wed, May 19, 2021 at 8:25 AM Jarek Potiuk <[email protected]> wrote: >>> >>>> Hello Everyone, >>>> >>>> I think we have one more last effort and we should be more vocal, >>>> explicit and active and make some campaign about the approaching Airflow >>>> 1.10 End-Of-Life. >>>> >>>> Let me know what you think? >>>> >>>> More context: >>>> >>>> The EOL for Airflow 1.10 is approaching fast. It's a MONTH from now: *June >>>> 17, 2021* (and I love it !). We've almost dropped all the baggage that >>>> it brought, but we keep on seeing some people still installing Airflow >>>> 1.10.12 (for example) as a "fresh" installation. >>>> >>>> I noticed that it's not really "prominently" displayed that 1.10 EOL is >>>> in June. When I looked for this information it's kind of missing: >>>> >>>> * you won't find it in the README.md >>>> https://github.com/apache/airflow/blob/master/README.md >>>> * you won't find it in the main documentation page of >>>> Airflow: >>>> https://airflow.apache.org/docs/apache-airflow/stable/index.html >>>> * you won't find it at the installation page: >>>> https://airflow.apache.org/docs/apache-airflow/stable/installation.html >>>> * you won't even explicitly find it in the upgrading page: >>>> https://airflow.apache.org/docs/apache-airflow/stable/upgrading-to-2.html >>>> >>>> The message there is "We strongly recommend that all users upgrading to >>>> Airflow 2.0, first upgrade to Airflow 1.10.15 and test their Airflow >>>> deployment and only then upgrade to Airflow 2.0. The Airflow 1.10.x release >>>> tree will be supported for six months from Airflow 2.0 release date." >>>> (of course you can calculate that but it requires looking up when >>>> Airflow 2.0 was released) >>>> * you won't even find it in our Planning page for Airflow 2.0: >>>> https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+2.0+-+Planning >>>> >>>> Should we make some more: >>>> >>>> * prominent changes to documentation/READMEs to explicitly state the >>>> date? >>>> * twitter/linkedin/social campaign announcing that the "end is near" ? >>>> * slack campaign with pinned reminder messages ? >>>> * banner on our website? >>>> * should we use Airflow Summit as a vehicle /campaign/announcements ? >>>> >>>> J. >>>> >>>> -- >>>> +48 660 796 129 >>>> >>>
