This is an automated email from the ASF dual-hosted git repository.

jedcunningham pushed a commit to branch v3-0-test
in repository https://gitbox.apache.org/repos/asf/airflow.git

commit b5c0f40da1206d06b7630050dce304a734541a8b
Author: Jed Cunningham <jedcunning...@apache.org>
AuthorDate: Thu Feb 20 14:34:47 2025 -0700

    Update RELEASE_NOTES.rst
---
 RELEASE_NOTES.rst               | 96 +++++++++++++++++++++++++++++++++++++++++
 airflow/reproducible_build.yaml |  4 +-
 docs/spelling_wordlist.txt      |  2 +
 3 files changed, 100 insertions(+), 2 deletions(-)

diff --git a/RELEASE_NOTES.rst b/RELEASE_NOTES.rst
index 780e33ee8e4..df7d4f98092 100644
--- a/RELEASE_NOTES.rst
+++ b/RELEASE_NOTES.rst
@@ -21,6 +21,102 @@
 
 .. towncrier release notes start
 
+Airflow 3.0.0b1 (2025-02-27)
+--------------------------------
+
+Airflow 3.0 is a huge milestone for the Airflow project; the first major 
release in over four years, and brings
+great improvements to the entire community.
+
+Highly requested UX features
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+DAG Versioning
+""""""""""""""
+
+Airflow now tracks DAG versions, providing better visibility into DAG changes 
over time. This enables users to view
+historical DAG run information, inspect historical DAG structures associated 
with that historical DAG run and execution states.
+
+Airflow now introduces DAG Bundles which allow tasks run with the correct code 
version even when DAGs evolve. Airflow also now
+supports the sourcing of these DAG bundles from multiple locations which 
enables more efficient DAG parsing and better control over refresh behaviour.
+
+Collectively, these improve observability and reliability across workflows.
+
+Modern Web Application
+""""""""""""""""""""""
+
+The Airflow UI is now completely React-based and fully API-driven using a new 
UI REST API.
+This overhaul improves user experience, maintainability and is a foundation 
for extensibility. Key feature enhancements include a new component-based 
design system
+(with dark mode) and an improved information architecture.
+
+We have also removed Flask AppBuilder as a core dependency. However, since FAB 
remains widely used for authentication and custom plugins,
+we have retained backwards compatibility for FAB plugins to ensure a smooth 
transition for users, while setting the stage for its eventual removal.
+
+Additionally, we have introduced a new flexible React-based plugin system to 
allow:
+- Custom widgets and information panels within the Grid View
+- Enhanced visibility of business-specific workflow details
+- Seamless integration of Airflow UI with external reporting tools like 
Grafana or Power BI
+
+Scheduler-managed Backfills
+"""""""""""""""""""""""""""
+
+In Airflow 3.0, Backfills are now first-class citizens, directly integrated 
into the Airflow scheduler. This enables better
+scalability, diagnostics, and support through the UI / API. This also 
eliminated redundancy in the scheduling logic, making Airflow more maintainable.
+
+Airflow 3.0 enables Tasks to be Run anywhere, at any time, in any language
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Task Execution Interface
+""""""""""""""""""""""""
+
+The Task Execution Interface evolves Airflow into a client / server 
architecture to enable easier upgrades, multi-cloud deployments, and 
multi-language support.
+This decouples task execution from Airflow internals, eliminating direct 
interaction from tasks with the Airflow metadatabase. These interactions
+now go through an API, which enables remote execution across network 
boundaries. This API based interaction also enables multi-language support
+for task execution while keeping DAGs in Python.
+Furthermore, this enhances security and scalability, reducing conflicts in 
dependency management.
+
+Edge Executor (Remote Task Execution)
+"""""""""""""""""""""""""""""""""""""
+
+The Edge Executor, designed for remote task execution across network 
boundaries is now based on the Task Execution Interface above.
+This enables seamless execution of tasks in remote environments without 
requiring direct database or message broker connections,
+making Airflow more scalable across diverse infrastructures.
+
+Data Assets and Event Driven Scheduling
+"""""""""""""""""""""""""""""""""""""""
+
+Airflow is evolving to be a more integrated part of the entire data ecosystem, 
in better understanding the data it
+operates on and to trigger DAGs based on changes in the surrounding data 
ecosystem.
+
+Asset-Centric Syntax
+""""""""""""""""""""
+
+Airflow evolution of Datasets into Data Assets enables it to better understand 
the data it orchestrates. Airflow 3 introduces
+the concept of Data Assets which go beyond physical Datasets such as tables 
and files to now expand to ML models, etc.
+Airflow 3 enables explicit definition of asset dependencies, making them 
easier to track and manage. The introduction of the
+@asset decorator streamlines defining assets within DAGs and clarifies 
dependency chains.
+
+
+External Event-Driven Scheduling in Airflow
+""""""""""""""""""""""""""""""""""""""""""""
+Airflow 3 introduces native event-driven capabilities, allowing DAGs to be 
triggered by external events like message queues.
+It builds on existing dataset-based scheduling (now referred to as Data 
Assets) and enhances monitoring, execution efficiency,
+and API support for event-based workflows.
+
+Enhanced Security in CLI via Integration of API
+"""""""""""""""""""""""""""""""""""""""""""""""
+
+Airflow 3 improves the security of Airflow and reduces the maintenance burden 
by having the CLI use the Airflow APIs
+(now significantly enhanced as detailed above). Evolving to have all access go 
through the APIs instead of direct database access
+is an important evolution for Airflow. This simplifies CLI deployment, reduces 
redundancy, and improves maintainability.
+
+Inference execution and hyper-parameter turning
+""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+
+Airflow currently uses execution_date to identify DAG runs, which introduces 
limitations, especially for dynamic workflows.
+In Airflow 3, execution_date has been renamed to logical_date and the 
constraint has selectively been removed to enable DAG
+execution for inference runs to be more intuitive and scalable.
+
+
 Airflow 2.10.5 (2025-02-10)
 ---------------------------
 
diff --git a/airflow/reproducible_build.yaml b/airflow/reproducible_build.yaml
index 0db388d56b9..9d8d30cb0c8 100644
--- a/airflow/reproducible_build.yaml
+++ b/airflow/reproducible_build.yaml
@@ -1,2 +1,2 @@
-release-notes-hash: 8c02811625ac7262d5ce34eb4cd7c5b0
-source-date-epoch: 1739197544
+release-notes-hash: 8bb0ea6c44a660252bca5e0b3ac45591
+source-date-epoch: 1740679597
diff --git a/docs/spelling_wordlist.txt b/docs/spelling_wordlist.txt
index 2f7a408bb1a..57de66244a6 100644
--- a/docs/spelling_wordlist.txt
+++ b/docs/spelling_wordlist.txt
@@ -741,6 +741,7 @@ googleapiclient
 GoogleDisplayVideo
 gpu
 gpus
+Grafana
 graphviz
 greenlet
 Groupalia
@@ -1414,6 +1415,7 @@ RefreshError
 regexes
 reidentify
 ReidentifyContentResponse
+reimagined
 reinit
 Reinitialising
 reinitialization

Reply via email to