added explaining concept of logical date in DAG run

[howardyoo]

Added two paragraphs under the DAG run to describe the difference between logical date and dag start and end date, and some of the reason behind its naming 'logical,' as well as providing an example. The intention for this additional content is to clarify any confusions about what logical date would mean compared to the DAG run's start and end date.

---

^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst)
Here are some useful points:

• Pay attention to the quality of your code (flake8, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it’s a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[uranusjr]

There are sections in DAG run and FAQ pages on this as well, it may be a good idea to link them together with seealso.

[howardyoo]

@uranusjr , I'm not sure which locations are you referring to in sections in DAG run and FAQ pages. Can you let me know so that I can perhaps create the seealso to it? Thanks!

[potiuk]

Hey @howardyoo - those are here:

• https://airflow.apache.org/docs/apache-airflow/stable/faq.html#what-does-execution-date-mean
• https://airflow.apache.org/docs/apache-airflow/stable/dag-run.html#data-interval

[potiuk]

And yeah I think we should aim to bring all those inter-connected. I think our docuemenation has too lttle interlinking and some information is repeated in places (and often some of the variants of the descriptions are out-dated).

I tend to simply run search/grep on similar terms when I update some documentation. Our documentation has pretty fast and good search (I know people aren't used to search in the documentation but I actually learned that the search here is actually very decent, fast and accurate :) https://airflow.apache.org/docs/apache-airflow/stable/index.html

[howardyoo]

Ok, added those references on each of the files mentioned above.

[potiuk]

LGTM. @uranusjr ?

[github-actions]

The PR is likely ready to be merged. No tests are needed as no important environment files, nor python files were modified by it. However, committers might decide that full test matrix is needed and add the 'full tests needed' label. Then you should rebase it to the latest main or amend the last commit of the PR, and push it with --force-with-lease.

[howardyoo]

done - I believe all the tests have succeeded, and the PR is ready to be merged.

[uranusjr]

Some thoughts on wording. Generally looks nice, thanks for taking the time to put this in words! It’s inheritantly a difficult thing to explain!

[boring-cyborg]

Awesome work, congrats on your first merged pull request!

[jedcunningham]

@howardyoo thanks! Congrats on your first commit 🎉

[howardyoo]

@howardyoo thanks! Congrats on your first commit 🎉

Thank you!! I hope for more to come! :-)