Hi all, I would like to remind whoever is interested in helping in Airflow 2.0 Release process that we will have our 2nd developer call today:
*Airflow 2.0 Dev Call Calendar Link*: https://calendar.google.com/calendar?cid=Y19kaGRoM2JkamM0MmM0bmd0bnBnN292Y3M5Z0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t *Time*: 5:30-6:30 PM GMT Some useful links: - 2.0 Milestone: https://github.com/apache/airflow/milestone/3 - Issue Tracker: https://github.com/apache/airflow/issues/10152 - Planning Doc & Meeting Notes: https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+2.0+-+Planning - Zoom Link: https://astronomer.zoom.us/j/94824827539?pwd=S3lYQkk2cUdnZEVxZ0V3SC9Xb29jUT09 Agenda for Today's call: - Process <https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+2.0+-+Planning#Airflow2.0Planning-Process:> - Decide on a date to create a 2.0.0-test branch - When should we defer the in-scope items to post-2.0 - Completion by a date? - Progress by a date? - Creating a Changelog for 2.0 - Discuss Challenges because of divergence from 1.10. - Updating guide should be more detailed, changelog needs to just show 1-line changes - More readable and categorized Changelog - Changelogs per provider - Release cadence for core/providers - Automation - ??? - Beta Testing - Need help from Airflow Vendors and power customers like Astronomer, Google - Polidea, AirBnb - Smart Sensors – in 2.0 or 2.1 - AIP-17 | PR: https://github.com/apache/airflow/pull/5499 - airflow upgrade-check <https://github.com/apache/airflow/issues/8765> command - Design discussion - Agreement on the scope - Get feedback on these DEV calls: - Do we increase the duration of the call or is it ideal --- ?? - Do we do more frequent calls ??? - Tracking the progress towards 2.0 - Discuss Agenda for Next Meetings Regards, Kaxil