[GitHub] [airflow] potiuk commented on a diff in pull request #26228: Prepare to release 2.4.0beta1

[GitBox <gi...@apache.org>]

potiuk commented on code in PR #26228:
URL: https://github.com/apache/airflow/pull/26228#discussion_r965751778


##########
RELEASE_NOTES.rst:
##########
@@ -21,6 +21,127 @@
 
 .. towncrier release notes start
 
+Airflow 2.4.0beta1 (2022-09-08)
+-------------------------------
+
+Significant Changes
+^^^^^^^^^^^^^^^^^^^
+
+- The DB related classes: ``DBApiHook``, ``SQLSensor`` have been moved to ``apache-airflow-providers-common-sql`` provider. (NEW)
+- DAGS used in a context manager no longer need to be assigned to a module variable
+
+  Previously you had do assign a DAG to a module-level variable in order for Airflow to pick it up. For example this
+
+  .. code-block:: python
+
+     with DAG(dag_id="example") as dag:
+         ...
+
+
+     @dag
+     def dag_maker():
+         ...
+
+
+     dag2 = dag_maker()
+
+
+  can become
+
+  .. code-block:: python
+
+     with DAG(dag_id="example"):
+         ...
+
+
+     @dag
+     def dag_maker():
+         ...
+
+
+     dag_maker()
+
+  If you want to disable the behaviour for any reason then set ``auto_register=False`` on the dag::
+
+  .. code-block::
+
+     # This dag will not be picked up by Airflow as it's not assigned to a variable
+     with DAG(dag_id="example", auto_register=False):
+        ...
+  (#23592)
+- DAG runs sorting logic changed in grid view
+
+  The ordering of DAG runs in the grid view has been changed to be more "natural".
+  The new logic generally orders by data interval, but a custom ordering can be
+  applied by setting the DAG to use a custom timetable. (#25090)
+- Deprecation of ``schedule_interval`` and ``timetable`` arguments
+
+  We added new DAG argument ``schedule`` that can accept a cron expression, timedelta object, *timetable* object, or list of dataset objects. Arguments ``schedule_interval`` and ``timetable`` are deprecated.
+
+  If you previously used the ``@daily`` cron preset, your DAG may have looked like this:
+
+  .. code-block:: python
+      with DAG(
+          dag_id='my_example',
+          start_date=datetime(2021, 1, 1),
+          schedule_interval='@daily',
+      ):
+          ...
+
+  Going forward, you should use the ``schedule`` argument instead:
+
+  .. code-block:: python
+      with DAG(
+          dag_id='my_example',
+          start_date=datetime(2021, 1, 1),
+          schedule='@daily',
+      ):
+          ...
+
+  The same is true if you used a custom timetable.  Previously you would have used the ``timetable`` argument:
+
+  .. code-block:: python
+      with DAG(
+          dag_id='my_example',
+          start_date=datetime(2021, 1, 1),
+          timetable=EventsTimetable(event_dates=[pendulum.datetime(2022, 4, 5)]),
+      ):
+          ...
+
+  Now you should use the ``schedule`` argument:
+
+  .. code-block:: python
+      with DAG(
+          dag_id='my_example',
+          start_date=datetime(2021, 1, 1),
+          schedule=EventsTimetable(event_dates=[pendulum.datetime(2022, 4, 5)]),
+      ):
+          ...
+
+  (#25410)
+- Removal of experimental Smart Sensors
+
+  Smart Sensors were added in 2.0 and deprecated in favour of Deferable operators in 2.2, and have now been removed. (#25507)
+- The ``contrib`` packages have now dynamically generated modules and while users can continue using the deprecated contrib classes, they are no longer visible for static code check tools and will be reported as missing. It is recommended for the users to move to non-deprecated classes. (#26153)

Review Comment:
   ```suggestion
   - The ``contrib`` packages anddeprecated moduiles from Airlfow 1.10 in "airflow.hooks", "airflow.operators", "airflow.sensors", have now dynamically generated modules and while users can continue using the deprecated contrib classes, they are no longer visible for static code check tools and will be reported as missing. It is recommended for the users to move to non-deprecated classes. (#26153, #26179, #26167)
   ```



-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org