This issue attempts to track the steps necessary to complete post-release maintenance tasks for 4.9.2.
The goal is to complete the following tasks, each task must have a PR associated with this issue.
The branches must follow the naming: merge-<ORIGIN_BRANCH>-into-<DESTINATION_BRANCH>. For example, merge-4.9.2-into-4.10.0.
Description
This issue attempts to track the steps necessary to complete post-release maintenance tasks for 4.9.2. The goal is to complete the following tasks, each task must have a PR associated with this issue.
The branches must follow the naming:
merge-<ORIGIN_BRANCH>-into-<DESTINATION_BRANCH>
. For example,merge-4.9.2-into-4.10.0
.Tasks
4.9.2
into branch4.10.0
.4.10.0
into branch4.10.1
.4.10.1
into branch4.10.2
.4.10.2
into branchmaster
.