This issue attempts to track the steps necessary to complete post-release maintenance tasks for 4.6.0.
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.6.0-into-4.7.0.
Tasks
[ ] Merge branch 4.6.0 into branch 4.7.0. Up to date.
[ ] Merge branch 4.7.0 into branch 4.7.1. Up to date.
[ ] Merge branch 4.7.1 into branch 4.8.0. Up to date.
[ ] Merge branch 4.8.0 into branch master. Up to date.
Description
This issue attempts to track the steps necessary to complete post-release maintenance tasks for 4.6.0. 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.6.0-into-4.7.0
.Tasks
Merge branchUp to date.4.6.0
into branch4.7.0
.Merge branchUp to date.4.7.0
into branch4.7.1
.Merge branchUp to date.4.7.1
into branch4.8.0
.Merge branchUp to date.4.8.0
into branchmaster
.4.6.0
.