kaxil commented on issue #11112: URL: https://github.com/apache/airflow/issues/11112#issuecomment-730463856
**Meeting - 19 Nov 2020** Attendees: Ash, Vikram, Jarek, Tomasz, Daniel, Kaxil - We will continue using v1-10-stable for upgrade_checks and the PRs targetted towards it. - We will support Airflow >=1.10.13 for upgrade_checks. - CI needs to be updated to test/support multiple versions. - Idea: Add a "version" field for checks to show supported Airflow version. - Ash to work on packaging and automation this/next week. - Add a check when using the plugin to see if a newer version of upgrade_check is available. Error / Warning ??? (This can be a Rule in upgrade-check itself) - If we include "--apply" flag that automatically fixes the code, we need to flag and WARN that to users that there will be **False positives** as Bowler is known to fail in some-cases (TypeHints). Have users confirm before apply any change and show the code diff that is being changed -- same as what Bowler does. - Where we don't automate, just verify we have it documented Release Management: - Have setup.py / setup.cfg inside airflow/upgrade_check folder (Ash to figure out details) ---------------------------------------------------------------- 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]
