Suggestion. If we think it's unclear - we can always vote on options. Present options and you set +1 in the option you prefer. Highest count wins.
Constance - maybe you can list the options and explain? My +1 one was on "Standardize on Dag" which means (for me): > Does this mean that we cannot use `dag` to refer informally to a dag in a sentence in the docs? > Like, would this be against the rules? Yes. > Given a start date and an end date, Airflow will create runs in the range according to the dag's schedule. > And we would have to do this instead? Yes. > Given a start date and an end date, Airflow will create runs in the range according to the Dag's schedule? > Does it also mean we can't use DAG? Yes. Daniel and others - maybe you can propose your proposal for the options we might have - that would likely make it easier for Constance to propose options ? We likely end up with three or four options to choose from. J. On Wed, Oct 15, 2025 at 7:29 PM Daniel Standish via dev < [email protected]> wrote: > Yeah the PR was merged but I'm sure many were not aware of it as it was not > like, brought to the list and voted on prior to making the PR. Indeed I > raised the discussion precisely because I saw the PR and I was like, wait > what? > > > > > On Wed, Oct 15, 2025 at 10:25 AM Constance Martineau via dev < > [email protected]> wrote: > > > s/not blocking/*now* blocking > > > > On Wed, Oct 15, 2025 at 1:24 PM Constance Martineau < > > [email protected]> > > wrote: > > > > > That's fair. To me, it seemed like we'd reached implicit consensus > since > > > the docs were already standardized on "Dag" and that PR was merged. > > > > > > I'm happy to reframe this as a clear vote between "dag", "Dag" or > "DAG". > > > What matters most is that we finally land on one and make it consistent > > > going forward. > > > > > > This has been open long enough that it's not blocking external > > > contributors and documentation alignment with external stakeholders, so > > I'd > > > really like to us to close the loop on this this week. > > > > > > On Wed, Oct 15, 2025 at 12:47 PM Josef Šimánek < > [email protected]> > > > wrote: > > > > > >> I prefer DAG, since it is what is actually imported. > > >> > > >> from airflow.sdk import DAG > > >> > > >> my_dag = DAG( > > >> dag_id="my_dag_name", > > >> start_date=datetime.datetime(2021, 1, 1), > > >> schedule="@daily", > > >> ) > > >> EmptyOperator(task_id="task", dag=my_dag) > > >> > > >> on the other side, there is also dag decorator > > >> > > >> from airflow.sdk import dag > > >> > > >> @dag(start_date=datetime.datetime(2021, 1, 1), schedule="@daily") > > >> def generate_dag(): > > >> EmptyOperator(task_id="task") > > >> > > >> It will be nice to pick the preferred way and keep the terminology > 1:1. > > >> > > >> út 14. 10. 2025 v 21:11 odesílatel Constance Martineau via dev > > >> <[email protected]> napsal: > > >> > > > >> > Hi everyone, > > >> > > > >> > Just to wrap up the dag vs DAG vs Dag nomenclature discussions we've > > >> been > > >> > having over the last few months, I would like to formally call a > vote > > to > > >> > standardize on "Dag". > > >> > > > >> > Jens already updated the docs for 3.1 via this PR > > >> > <https://github.com/apache/airflow/pull/55097>, so hopefully this > is > > >> just a > > >> > formality. > > >> > > > >> > Discussion threads: > > >> > > > >> > - > https://lists.apache.org/thread/lktrzqkzrpvc1cyctxz7zxfmc0fwtq2j > > >> > - > https://lists.apache.org/thread/5fn1n188f99jspt627qhqsp2pznq545s > > >> > > > >> > > > >> > Thank you to everyone who took part in the conversations. The vote > > will > > >> run > > >> > for ~3 days, and last till Friday October 17, 2025 at 7:30pm > > (countdown > > >> link > > >> > <https://countingdownto.com/?c=6644364>). > > >> > > > >> > Everyone is encouraged to vote, although only PMC members and > > >> Committer's > > >> > votes are considered binding. > > >> > > > >> > Please consider this my +1 (non-binding). > > >> > -- > > >> > > > >> > Constance > > >> > > > > > >
