Thanks for the pointer. I'll move the comments from the PR to the github discussion and continue usage/technical discussion there. In the meantime, I'd like to discuss a bit on what is the best way to release such change.
Replacing one of the most used interfaces is a pretty big deal. I like the grid view but it is not a superset of tree view, thus user workflows can break with the change. Yes we can argue that people can update their workflow and get used to it. But I'm not quite sure "we changed it to this, get used to it" is always the best approach we take to make Airflow a success when it's not strictly an improvement. I do understand that we want to move fast. But as an established project widely used by many companies in production to power their business, we can maybe at the same time give more buffer for such change and incorporate more feedback. Like how we do deprecation, give people some time to react. People would naturally move to it if they find themselves much more productive using it. DAG versioning is very nice and I want it badly too. However I see it depends on the grid view but not the deprecation of tree view--we can always claim that tree view does not support versioning, another soft push for people to use grid view 😁 Hope I'm making sense, looking forward to hearing your thoughts. Cheers, Kevin Y On Tue, May 3, 2022 at 12:19 PM Brent Bovenzi <br...@astronomer.io.invalid> wrote: > Seconding what Jarek said. Please comment in that github discussion. I > would very much like to get feedback and then iterate the UI much faster > than before. > > On Tue, May 3, 2022 at 3:14 PM Jarek Potiuk <ja...@potiuk.com> wrote: > >> I personally don't think so. >> >> People will have to get used to it. It's far superior. And backlash is >> expected. >> >> I would rather read and focus on what's there to make it respond to the >> needs of users than have it in parallel with Tree view. Discussion already >> started here https://github.com/apache/airflow/discussions/23413 and I'd >> say we should do everything to figure out what people REALLY miss in the >> Grid View comparing to Tree view and iterate on it and add it (And from >> earlier discussions with Brent, I think this is the plan). >> >> The Tree view held us back like crazy. >> >> The biggest problem with Tree view was that DAG versioning effort was (I >> believe) held back by it because it was next to impossible to think of >> "versioning" when Tree view was there. >> >> This is a bold move - but very much needed and even overdue I think. >> >> J. >> >> >> On Tue, May 3, 2022 at 9:05 PM Kevin Yang <yrql...@gmail.com> wrote: >> >>> Hey guys sorry I saw this thread late--was on vacation last week. >>> >>> I noticed that we made a bold move replacing the tree view with the new >>> grid view. I like the new grid view, but given the open discussion in this >>> PR <https://github.com/apache/airflow/pull/18675> and popularity of >>> tree view (in our use case it's visited 13x times more than graph view), >>> should we consider making it an *addition* for now rather than >>> *replacement*? >>> >>> On Sat, Apr 30, 2022 at 9:48 AM Kaxil Naik <kaxiln...@gmail.com> wrote: >>> >>>> +1 (binding) - Big milestone since 2.0 >>>> >>>> On Sat, 30 Apr 2022 at 09:24, Jarek Potiuk <ja...@potiuk.com> wrote: >>>> >>>>> Fanatic -> fantastic work... Seems like some drag&drop issue with my >>>>> Chrome :) >>>>> >>>>> J >>>>> >>>>> On Sat, Apr 30, 2022 at 10:21 AM Jarek Potiuk <ja...@potiuk.com> >>>>> wrote: >>>>> > >>>>> > +1 (binding). Checked signatures, licences, checksums. All looks >>>>> good. >>>>> > >>>>> > There is a TON of cool stuff in this release. I am confident it's >>>>> > ready to get to the hands of our users after all the fanatic plenty >>>>> of >>>>> > people put in it. Just two things that I think deserve highlighting: >>>>> > >>>>> > * There is the obvious Dynamic Task Mapping (which is the highlight >>>>> of >>>>> > it - Ash and TP particularly - but all the other people who tested it >>>>> > have spent countless hours on it and it is life- and future- changing >>>>> > for Airflow). >>>>> > * I particularly like the new Grid View. It will take people a bit of >>>>> > getting used to the new screen - so this is a bit of a bold move and >>>>> > there will be backlash I am sure. But I am quite confident it is >>>>> soooo >>>>> > much better and makes Airflow 2.3 finally showing up the modern UI >>>>> > approach as well (After all the internal modernization) . >>>>> > Brent and the team - big Kudos for all the work there and the >>>>> boldness >>>>> > in rethinking this one from grounds-up :). >>>>> > >>>>> > J. >>>>> > >>>>> > >>>>> > On Fri, Apr 29, 2022 at 10:28 PM Vikram Koka >>>>> > <vik...@astronomer.io.invalid> wrote: >>>>> > > >>>>> > > +1 (non-binding) >>>>> > > >>>>> > > Dynamic Task Mapping is a huge improvement! >>>>> > > >>>>> > > On Fri, Apr 29, 2022 at 11:34 AM Josh Fell < >>>>> josh.d.f...@astronomer.io.invalid> wrote: >>>>> > >> >>>>> > >> +1 (non-binding) >>>>> > >> >>>>> > >> Dynamic Task Mapping feels life-changing. >>>>> > >> >>>>> > >> On Fri, Apr 29, 2022 at 12:41 PM Abhishek Bhakat >>>>> <abhishek.bha...@astronomer.io.invalid> wrote: >>>>> > >>> >>>>> > >>> Other than that issue, have tested the version and would like to >>>>> change my vote to +1 (non-binding) >>>>> > >>> >>>>> > >>> On Fri, Apr 29, 2022 at 9:49 PM Elad Kalif <elad...@apache.org> >>>>> wrote: >>>>> > >>>> >>>>> > >>>> +1 (binding) >>>>> > >>>> >>>>> > >>>> On Fri, Apr 29, 2022 at 6:34 PM Dennis Akpenyi < >>>>> dennisakpe...@gmail.com> wrote: >>>>> > >>>>> >>>>> > >>>>> +1 (non-binding) >>>>> > >>>>> >>>>> > >>>>> On Fri 29. Apr 2022 at 17:30, Brent Bovenzi >>>>> <br...@astronomer.io.invalid> wrote: >>>>> > >>>>>> >>>>> > >>>>>> +1 (non-binding) >>>>> > >>>>>> >>>>> > >>>>>> On Fri, Apr 29, 2022 at 11:13 AM Ash Berlin-Taylor < >>>>> a...@apache.org> wrote: >>>>> > >>>>>>> >>>>> > >>>>>>> No, the same issue is fine. >>>>> > >>>>>>> >>>>> > >>>>>>> My point is that since this is no worse in 2.3.0rc2 than it >>>>> was in 2.2.5 it shouldn't stop the release of 2.3.0. >>>>> > >>>>>>> >>>>> > >>>>>>> Cheers, >>>>> > >>>>>>> Ash >>>>> > >>>>>>> >>>>> > >>>>>>> On Fri, Apr 29 2022 at 20:28:49 +0530, Abhishek Bhakat >>>>> <abhishek.bha...@astronomer.io.INVALID> wrote: >>>>> > >>>>>>> >>>>> > >>>>>>> I am facing this issue with 2.3.0rc2. I did make a comment >>>>> on the same issue. Shall I create another issue for 2.3.0rc2 ? >>>>> > >>>>>>> >>>>> > >>>>>>> On Fri, Apr 29, 2022 at 8:20 PM Ash Berlin-Taylor < >>>>> a...@apache.org> wrote: >>>>> > >>>>>>>> >>>>> > >>>>>>>> Hi Abhishek, >>>>> > >>>>>>>> >>>>> > >>>>>>>> The issue you have linked to says the version that happens >>>>> is in 2.2.5, so since this isn't a regression in 2.3 I'd ask if you could >>>>> remove your -1 vote? >>>>> > >>>>>>>> >>>>> > >>>>>>>> On Fri, Apr 29 2022 at 20:13:31 +0530, Abhishek Bhakat >>>>> <abhishek.bha...@astronomer.io.INVALID> wrote: >>>>> > >>>>>>>> >>>>> > >>>>>>>> -1 (non-binding) >>>>> > >>>>>>>> An issue with parsing dynamic tasks, causes the scheduler >>>>> to crash. >>>>> > >>>>>>>> https://github.com/apache/airflow/issues/23361 >>>>> > >>>>>>>> >>>>> > >>>>>>>> On Fri, Apr 29, 2022 at 7:58 PM Collin McNulty >>>>> <col...@astronomer.io.invalid> wrote: >>>>> > >>>>>>>>> >>>>> > >>>>>>>>> +1 (non-binding) >>>>> > >>>>>>>>> >>>>> > >>>>>>>>> Made and ran several test DAGs using mapped tasks. >>>>> > >>>>>>>>> >>>>> > >>>>>>>>> On Fri, Apr 29, 2022 at 3:54 AM Ash Berlin-Taylor < >>>>> a...@apache.org> wrote: >>>>> > >>>>>>>>>> >>>>> > >>>>>>>>>> +1 binding. >>>>> > >>>>>>>>>> >>>>> > >>>>>>>>>> On Wed, Apr 27 2022 at 21:50:48 +0100, Ephraim Anierobi < >>>>> ephraimanier...@apache.org> wrote: >>>>> > >>>>>>>>>> >>>>> > >>>>>>>>>> Hey fellow Airflowers, >>>>> > >>>>>>>>>> >>>>> > >>>>>>>>>> I have cut Airflow 2.3.0rc2. This email is calling a vote >>>>> on the release, >>>>> > >>>>>>>>>> which will last for 72 hours, from Wednesday, April 27, >>>>> 2022, at 08:48 pm UTC >>>>> > >>>>>>>>>> until Saturday, April 30, 2022, at 08:48 pm UTC, and >>>>> until 3 binding +1 votes have been received. >>>>> > >>>>>>>>>> >>>>> > >>>>>>>>>> Consider this my (binding) +1. >>>>> > >>>>>>>>>> >>>>> > >>>>>>>>>> Airflow 2.3.0rc2 is available at: >>>>> > >>>>>>>>>> https://dist.apache.org/repos/dist/dev/airflow/2.3.0rc2/ >>>>> > >>>>>>>>>> >>>>> > >>>>>>>>>> *apache-airflow-2.3.0-source.tar.gz* is a source release >>>>> that comes with INSTALL instructions. >>>>> > >>>>>>>>>> *apache-airflow-2.3.0.tar.gz* is the binary Python >>>>> "sdist" release. >>>>> > >>>>>>>>>> *apache_airflow-2.3.0-py3-none-any.whl* is the binary >>>>> Python wheel "binary" release. >>>>> > >>>>>>>>>> >>>>> > >>>>>>>>>> Public keys are available at: >>>>> > >>>>>>>>>> https://dist.apache.org/repos/dist/release/airflow/KEYS >>>>> > >>>>>>>>>> >>>>> > >>>>>>>>>> Please vote accordingly: >>>>> > >>>>>>>>>> >>>>> > >>>>>>>>>> [ ] +1 approve >>>>> > >>>>>>>>>> [ ] +0 no opinion >>>>> > >>>>>>>>>> [ ] -1 disapprove with the reason >>>>> > >>>>>>>>>> >>>>> > >>>>>>>>>> Only votes from PMC members are binding, but all members >>>>> of the community >>>>> > >>>>>>>>>> are encouraged to test the release and vote with >>>>> "(non-binding)". >>>>> > >>>>>>>>>> >>>>> > >>>>>>>>>> The test procedure for PMCs and Contributors who would >>>>> like to test this RC are described in >>>>> > >>>>>>>>>> >>>>> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_AIRFLOW.md\#verify-the-release-candidate-by-pmcs >>>>> > >>>>>>>>>> >>>>> > >>>>>>>>>> Please note that the version number excludes the `rcX` >>>>> string, so it's now >>>>> > >>>>>>>>>> simply 2.3.0. This will allow us to rename the artifact >>>>> without modifying >>>>> > >>>>>>>>>> the artifact checksums when we actually release. >>>>> > >>>>>>>>>> >>>>> > >>>>>>>>>> Release Notes: >>>>> https://github.com/apache/airflow/blob/2.3.0rc2/RELEASE_NOTES.rst >>>>> > >>>>>>>>>> >>>>> > >>>>>>>>>> New features since 2.2.5: >>>>> > >>>>>>>>>> >>>>> > >>>>>>>>>> - Add dynamic task mapping ( >>>>> https://github.com/apache/airflow/pulls?q=is%3Apr+is%3Amerged+label%3AAIP-42+milestone%3A%22Airflow+2.3.0%22 >>>>> ) >>>>> > >>>>>>>>>> - New Grid View replaces Tree View (#18675) >>>>> > >>>>>>>>>> - Templated ``requirements.txt`` in Python Operators >>>>> (#17349) >>>>> > >>>>>>>>>> - Allow reuse of decorated tasks (#22941) >>>>> > >>>>>>>>>> - Move the database configuration to a new section >>>>> (#22284) >>>>> > >>>>>>>>>> - Add ``SmoothOperator`` (#22813) >>>>> > >>>>>>>>>> - Make operator's ``execution_timeout`` configurable >>>>> (#22389) >>>>> > >>>>>>>>>> - Events Timetable (#22332) >>>>> > >>>>>>>>>> - Support dag serialization with custom ``ti_deps`` rules >>>>> (#22698) >>>>> > >>>>>>>>>> - Support log download in task log view (#22804) >>>>> > >>>>>>>>>> - support for continue backfill on failures (#22697) >>>>> > >>>>>>>>>> - Add ``dag-processor`` cli command (#22305) >>>>> > >>>>>>>>>> - Add possibility to create users in LDAP mode (#22619) >>>>> > >>>>>>>>>> - Add ``ignore_first_depends_on_past`` for scheduled jobs >>>>> (#22491) >>>>> > >>>>>>>>>> - Update base sensor operator to support XCOM return >>>>> value (#20656) >>>>> > >>>>>>>>>> - Add an option for run id in the ui trigger screen >>>>> (#21851) >>>>> > >>>>>>>>>> - Enable JSON serialization for connections (#19857) >>>>> > >>>>>>>>>> - Add REST API endpoint for bulk update of DAGs (#19758) >>>>> > >>>>>>>>>> - Add queue button to click-on-DagRun interface. (#21555) >>>>> > >>>>>>>>>> - Add ``list-import-errors`` to ``airflow dags`` command >>>>> (#22084) >>>>> > >>>>>>>>>> - Store callbacks in database if >>>>> ``standalone_dag_processor`` config is True. (#21731) >>>>> > >>>>>>>>>> - Add LocalKubernetesExecutor (#19729) >>>>> > >>>>>>>>>> - Add ``celery.task_timeout_error`` metric (#21602) >>>>> > >>>>>>>>>> - Airflow ``db downgrade`` cli command (#21596) >>>>> > >>>>>>>>>> - Add ``ALL_SKIPPED`` trigger rule (#21662) >>>>> > >>>>>>>>>> - Add ``db clean`` CLI command for purging old data >>>>> (#20838) >>>>> > >>>>>>>>>> - Add ``celery_logging_level`` (#21506) >>>>> > >>>>>>>>>> - Support different timeout value for dag file parsing >>>>> (#21501) >>>>> > >>>>>>>>>> - Support generating SQL script for upgrades (#20962) >>>>> > >>>>>>>>>> - Add option to compress Serialized dag data (#21332) >>>>> > >>>>>>>>>> - Branch python operator decorator (#20860) >>>>> > >>>>>>>>>> - Add Audit Log View to Dag View (#20733) >>>>> > >>>>>>>>>> - Add missing StatsD metric for failing SLA Callback >>>>> notification (#20924) >>>>> > >>>>>>>>>> - Add ``ShortCircuitOperator`` configurability for >>>>> respecting downstream trigger rules (#20044) >>>>> > >>>>>>>>>> - Allow using Markup in page title in Webserver (#20888) >>>>> > >>>>>>>>>> - Add Listener Plugin API that tracks TaskInstance state >>>>> changes (#20443) >>>>> > >>>>>>>>>> - Add context var hook to inject more env vars (#20361) >>>>> > >>>>>>>>>> - Add a button to set all tasks to skipped (#20455) >>>>> > >>>>>>>>>> - Cleanup pending pods (#20438) >>>>> > >>>>>>>>>> - Add config to warn public deployment exposure in UI >>>>> (#18557) >>>>> > >>>>>>>>>> - Log filename template records (#20165) >>>>> > >>>>>>>>>> - Added windows extensions (#16110) >>>>> > >>>>>>>>>> - Showing approximate time until next dag_run in Airflow >>>>> (#20273) >>>>> > >>>>>>>>>> - Extend config window on UI (#20052) >>>>> > >>>>>>>>>> - Add show dag dependencies feature to CLI (#19985) >>>>> > >>>>>>>>>> - Add cli command for 'airflow dags reserialize` (#19471) >>>>> > >>>>>>>>>> - Add missing description field to Pool schema(REST API) >>>>> (#19841) >>>>> > >>>>>>>>>> - Introduce DagRun action to change state to queued. >>>>> (#19353) >>>>> > >>>>>>>>>> - Add DAG run details page (#19705) >>>>> > >>>>>>>>>> - Add role export/import to cli tools (#18916) >>>>> > >>>>>>>>>> - Adding ``dag_id_pattern`` parameter to the ``/dags`` >>>>> endpoint (#18924) >>>>> > >>>>>>>>>> >>>>> > >>>>>>>>>> Thanks >>>>> > >>>>>>>>>> Ephraim >>>>> > >>>>> >>>>> > >>>>> -- >>>>> > >>>>> Dr. Dennis Akpenyi, Airflow Core Developer, Astronomer Inc. >>>>> >>>>
