[GitHub] [airflow-site] jedcunningham commented on a diff in pull request #699: Short blog post and announcment for 2.5 release

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

jedcunningham commented on code in PR #699:
URL: https://github.com/apache/airflow-site/pull/699#discussion_r1038320012


##########
landing-pages/site/content/en/blog/airflow-2.5.0/index.md:
##########
@@ -0,0 +1,55 @@
+---
+title: "Apache Airflow 2.5.0: tick-tock"
+linkTitle: "Apache Airflow 2.5.0"
+author: "Ash Berlin-Taylor"
+github: "ashberlin"
+twitter: "ashberlin"
+linkedin: "ashberlin-taylor"
+description: "We're proud to announce that Apache Airflow 2.5.0 has been released many quality of life changes."
+tags: [Release]
+date: "2022-09-19"
+---
+
+Apache Airfow 2.5 has just been released, barely two and a half months after 2.4!
+
+
+**Details**:
+
+📦 PyPI: https://pypi.org/project/apache-airflow/2.5.0/ \
+📚 Docs: https://airflow.apache.org/docs/apache-airflow/2.5.0/ \
+🛠️ Release Notes: https://airflow.apache.org/docs/apache-airflow/2.5.0/release_notes.html \
+🐳 Docker Image: docker pull apache/airflow:2.5.0 \
+🚏 Constraints: https://github.com/apache/airflow/tree/constraints-2.5.0
+
+This quicker release cadance is a departure from our previous habit of releasing every five-to-seven months and was a delibarate effort to listen to you, our users, and get the changes and improvments into your workflows sooner.
+
+## Usability improvements to the Datasets UI
+
+When we released Dataset aware scheduling in September we knew that the tools we gave to manage the Datasets were very much a Minimum Viable Product, and in the last two months the committers and contributors have been hard at work at making the UI much more usable when it comes to Datasets.
+
+But we we aren't done yet - keep an eye out for more improvments coming over the next couple of releases too.
+
+## Greatly improved `airflow dags test` command
+
+This airflow subcommand has been rethought and re-optimized to make it much easier to test your DAGs locally - the major changes are:
+
+a. Task logs are visible right there in the console, instead of hidden away inside the task log files
+b. It is about an order of mangnitude quicker to run the tasks than before (i.e. it gets to running the task code so much quicker); and
+c. Everything runs in one process, so you can put a breakpoint in your IDE, and configure it to run `airflow dags test <mydag>` then debug code!
+
+## Auto tailing task logs in the Grid view
+
+Hopefully the headline point says enough. It's lovely, go check it out.

Review Comment:
   ```suggestion
   Hopefully the headline says enough. It's lovely, go check it out.
   ```



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