Keep tracking with latest TiDB Dashboard
According to the current TiDB Dashboard versioning policy, PD branches since v5.4.0 should keep track with the latest TiDB Dashboard release. On the other hand, TiDB Dashboard should ensure that each release is compatible with latest commits of these PD branches.
This issue will be kept open, until someday TiDB Dashboard becomes an independent deployed component.
The version matrix between TiDB Dashboard release and PD release
| PD VERSION | PD COMMIT AT | TIDB DASHBOARD VERSION |
|---|---|---|
| v4.0.3 | 2020-07-21 | 2020.07.15.1 |
| v4.0.4 | 2020-07-21 | 2020.07.15.1 |
| v4.0.5 | 2020-08-27 | 2020.08.07.1 |
| v4.0.6 | 2020-09-08 | 2020.09.08.1 |
| v4.0.7 | 2020-09-21 | 2020.09.21.1 |
| v4.0.8 | 2020-10-22 | 2020.10.21.1 |
| v4.0.9 | 2020-12-01 | 2020.11.26.1 |
| v4.0.10 | 2021-01-06 | 2020.11.26.1 |
| v4.0.11 | 2021-01-28 | 2021.01.04.1 |
| v4.0.12 | 2021-03-25 | 2021.01.04.1 |
| v4.0.13 | 2021-05-13 | 2021.05.12.1 |
| v4.0.14 | 2021-07-17 | 2021.07.17.1 |
| v4.0.15 | 2021-09-09 | 2021.08.26.2 |
| v4.0.16 | 2021-11-30 | 2021.08.26.2 |
| v5.0.0 | 2021-03-26 | 2021.03.19.1 |
| v5.0.1 | 2021-04-16 | 2021.03.19.1 |
| v5.0.2 | 2021-06-01 | 2021.05.12.1 |
| v5.0.3 | 2021-06-28 | 2021.06.15.1 |
| v5.0.4 | 2021-09-06 | 2021.08.26.2 |
| v5.0.5 | 2021-09-06 | 2021.08.26.2 |
| v5.0.6 | 2021-12-21 | 2021.09.02.r40.1 |
| v5.1.0 | 2021-06-18 | 2021.06.15.1 |
| v5.1.1 | 2021-07-23 | 2021.07.17.1 |
| v5.1.2 | 2021-09-15 | 2021.08.26.2 |
| v5.1.3 | 2021-09-15 | 2021.08.26.2 |
| v5.1.4 | 2022-01-26 | 2021.09.02.r40.1 |
| v5.2.0 | 2021-08-26 | 2021.08.26.1 |
| v5.2.1 | 2021-08-26 | 2021.08.26.1 |
| v5.2.2 | 2021-10-19 | 2021.10.08.1 |
| v5.2.3 | 2021-10-19 | 2021.10.08.1 |
| v5.2.4 | 2022-04-14 | 2021.09.02.r52.2 |
| v5.3.0 | 2021-11-16 | 2021.11.08.1 |
| v5.3.1 | 2022-02-23 | 2021.12.06.1 |
| v5.4.0 | 2022-01-17 | 2022.01.17.1 |
| v5.4.1 | 2022-04-26 | 2022.01.17.1 |
| v6.0.0 | 2022-03-31 | 2022.03.31.1 |
Note: This issue is a collection issue for the following issues and aims to reduce some manual maintenance effort.
- https://github.com/tikv/pd/issues/4300
- https://github.com/tikv/pd/issues/4247
- https://github.com/tikv/pd/issues/3863
- https://github.com/tikv/pd/issues/3573
- https://github.com/tikv/pd/issues/3021
@breeswish: The label(s) type/type/enhancement cannot be applied, because the repository doesn't have them.
In response to this:
/type type/enhancement
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.
@breeswish: The label(s) type/type/enhancement cannot be applied, because the repository doesn't have them.
In response to this:
/type type/enhancement
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.
for release-5.3 see #4300
Please help re-open this issue, it needs to be always open.
Do we have dashboard update rules? Is the 5.0 branch need to keep up-to-date? cc @breeswish
@nolouch The 4.0.x ~ 5.1.x branch of tracking TiDB Dashboard is currently frozen, since new releases are unstable and we cannot ensure its quality. We will begin tracking later when there are enough tests.