XD-DENG commented on a change in pull request #13813:
URL: https://github.com/apache/airflow/pull/13813#discussion_r562150046
##########
File path: CONTRIBUTING.rst
##########
@@ -383,24 +383,40 @@ Airflow Git Branches
====================
All new development in Airflow happens in the ``master`` branch. All PRs
should target that branch.
-We also have a ``v1-10-test`` branch that is used to test ``1.10.x`` series of
Airflow and where committers
+
+
+We also have a ``v2-0-test`` branch that is used to test ``2.0.x`` series of
Airflow and where committers
cherry-pick selected commits from the master branch.
+
Cherry-picking is done with the ``-x`` flag.
-The ``v1-10-test`` branch might be broken at times during testing. Expect
force-pushes there so
-committers should coordinate between themselves on who is working on the
``v1-10-test`` branch -
+The ``v2-0-test`` branch might be broken at times during testing. Expect
force-pushes there so
+committers should coordinate between themselves on who is working on the
``v2-0-test`` branch -
usually these are developers with the release manager permissions.
-Once the branch is stable, the ``v1-10-stable`` branch is synchronized with
``v1-10-test``.
-The ``v1-10-stable`` branch is used to release ``1.10.x`` releases.
+The ``v2-0-stable`` branch is rather stable - there are minimum changes coming
from approved PRs that
+passed the tests. This means that the branch is rather, well, "stable".
+
+Once the branch is stable, the ``v2-0-stable`` branch is synchronized with
``v2-0-test``.
Review comment:
`Once the branch is stable` is not clear here, because of the new
paragraph added above.
```suggestion
Once ``v2-0-test`` is stable, the ``v2-0-stable`` branch is synchronized
with ``v2-0-test``.
```
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
