release: v7.5.3

[Ivy-YinSu]

Disclaimer

The dates published in this issue are for planning purposes only. It is intended solely to help you plan your projects. A date that exists in the future should not be considered a firm release date as the release and timing of releases are subject to change at any time and are at PingCAP's sole discretion.

Candidate SHA:

TiDB: 70bfd90
TiKV: 7b111327c4e6f5bb1ebcde84299343a4c13b4e09
PD: fcb34c90790c75553ccd52e1f748c41fcbb1c7b5
TiFlash: 8ed983598006ac5221574e441972488bfd458133
binlog: 35b674dea9c4f3184a7e86800ab83b9c5504fc3d
tidb-tools: 202dcf9d60734092a54d17181c268dfd0b3645c9
tiflow: c7a55133c7f351a7bae66a3c03fffed34ed3e153
ng-monitoring: c0cf08c686061d5f88b0c964911de4f121d8b4d1
enterprise-plugin: 8be043bea8690532cbd6949fae8ee1539e375d29
dumpling: 70bfd90
tidb-dashboard: 2b0fa9814c503942d0c03e0676459bb164d541c8
monitoring: d43fab18f11ce991337cd5fc537601b0333a601d

Working Tags: v7.5.3

Check the diff in the current version:

See the difference from the commit perspective:
TiDB diff
TiKV diff
PD diff
TiFlash diff
tidb-binlog diff
tidb-tools diff
ticdc diff
dm diff

Release process checklist

• 0. Announce the release plan.
• 1. Code freeze and RC build: Jul. 23, 2024
• 2. Qualifying the release.
• 3. Docs preparing for release.
• 4. The release qualified.
• 5. Docs are ready for release.

Release date: Aug. 5, 2024

Do not proceed below until the release date.

• 6. Publish TiDB Release

• fill in Candidate SHA above
• fill in the release tag

• 7. Update docs
• 8. Update the official website

[Ivy-YinSu]

Hello Everyone,
We are sorry to announce that TiDB v7.5.3 release will be postponed from 2024/07/31 to 2024/08/05.

Reason and next plan:
Reason
The tidb issue 54897 may cause a newly created index to have the data inconsistent problem.
Issue 54897 introduced by feature 35983 from v6.5.0-LTS.
Low recurrence probability until recently
Next plan
Add testcases into our HA test set and properly verify that the fix completely fixes the issue and to make sure there is no new problem that is introduced by the fix.
We are strictly following the release schedule, but the current issue has the potential to introduce data consistency issues that carry quality risks. After a careful assessment, it needs to be resolved before release.