Hello fellow Airflowers, Following up on the dev call notes regarding addressing open Github items and the conversation around key areas, I ran a quick analysis on all the open Github issues since the Airflow 3.0 release.
The focus here is really on the "Core Airflow" issues, rather on providers and such, but for completeness, those are shown here as well. Within the Core Airflow breakdown, please note that there can be duplication within the labels since a Github issue can have multiple labels. For example, the performance label is duplicated with which component is being reported on. That's reflected on the Airflow 3.x wiki page <https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+3.x> - the adoption focus section. My ask here is to continue to report issues as you find them, to categorize them appropriately, and to help work on areas that you are most familiar with. Thank you and best regards, Vikram Open issues by area (total=295): area_label count percent ---------------------------------- core 210 71.2% providers 69 23.4% helm-chart 16 5.4% unlabeled_for_area 0 0.0% Core Airflow breakdown: area_label count percent --------------------------------------------------- area:UI 52 24.8% area:Scheduler 27 12.9% area:logging 18 8.6% area:API 17 8.1% area:auth 13 6.2% area:data-aware-scheduling 10 4.8% area:MetaDB 8 3.8% area:dynamic-task-mapping 8 3.8% area:performance 5 2.4% area:task-sdk 5 2.4% area:CLI 4 1.9% area:TaskGroup 4 1.9% area:secrets 4 1.9% area:Triggerer 3 1.4% area:backfill 3 1.4% area:plugins 3 1.4% area:task-execution-interface-aip72 3 1.4% area:metrics 2 1.0% area:serialization 2 1.0% area:Executors-core 1 0.5% area:airflow-ctl 1 0.5% area:async-operators 1 0.5% area:db-migrations 1 0.5% -- Vikram Koka Chief Strategy Officer Email: [email protected] <https://www.astronomer.io/>
