[airflow] branch master updated: Improve language of a BaseSensorOperator in UPDATING.md (#10332)

[po...@apache.org]

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

potiuk pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/master by this push:
     new 6656464  Improve language of a BaseSensorOperator in UPDATING.md (#10332)
6656464 is described below

commit 6656464772bd5975f7d6e9b4c0b74963350f2a9d
Author: Kaxil Naik <ka...@gmail.com>
AuthorDate: Sat Aug 15 21:23:47 2020 +0100

    Improve language of a BaseSensorOperator in UPDATING.md (#10332)
---
 UPDATING.md | 17 ++++++++---------
 1 file changed, 8 insertions(+), 9 deletions(-)

diff --git a/UPDATING.md b/UPDATING.md
index 2b99d44..7392acc 100644
--- a/UPDATING.md
+++ b/UPDATING.md
@@ -569,15 +569,14 @@ release may contain changes that will require changes to your DAG files.
 This section describes the changes that have been made, and what you need to do to update your DAG File,
 if you use core operators or any other.
 
-#### BaseSensorOperator to make respect the trigger_rule of downstream tasks
-
-Previously, BaseSensorOperator with setting soft_fail=True becomes skipped itself
-and skips all its downstream tasks unconditionally, when it fails.
-The point is not respect the trigger_rule of downstream tasks, when it fails.
-In the new behavior, the trigger_rule of downstream tasks are respected.
-User can preserve/achieve the original behaviour by setting every downstream task to all_success,
-because downstream tasks with trigger_rule all_success (i.e. the default) are skipped
-when upstream task is skipped.
+#### BaseSensorOperator now respects the trigger_rule of downstream tasks
+
+Previously, BaseSensorOperator with setting `soft_fail=True` skips itself
+and skips all its downstream tasks unconditionally, when it fails i.e the trigger_rule of downstream tasks is not
+respected.
+
+In the new behavior, the trigger_rule of downstream tasks is respected.
+User can preserve/achieve the original behaviour by setting the trigger_rule of each downstream task to `all_success`.
 
 #### BaseOperator uses metaclass