new nav release-6.1: remove develop guide, releases, and best practices from TOC.md

[qiancai]

What is changed, added or deleted? (Required)

• Removed doc entries for Develop/Best Practices/Release Notes
• Moved TiDB Installation Packages from the Release Notes category to the References category
• Moved java-app-best-practices.md to develop/.

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

• master (the latest development version)
• v9.0 (TiDB 9.0 versions)
• v8.5 (TiDB 8.5 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)
• v6.1 (TiDB 6.1 versions)
• v5.4 (TiDB 5.4 versions)

What is the related PR or file link(s)?

• This PR is translated from:
• Other reference link(s):

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign lichunzhu for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[gemini-code-assist]

Summary of Changes

Hello @qiancai, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the documentation structure by removing several top-level categories from the Table of Contents and reorganizing specific files. These changes aim to improve the overall navigability and logical grouping of content, making it easier for users to find relevant information within the documentation.

Highlights

• Table of Contents Restructuring: Removed the 'Develop', 'Best Practices', and 'Release Notes' sections from the main Table of Contents (TOC.md) to streamline navigation.
• Documentation Relocation: Relocated the 'TiDB Installation Packages' entry within TOC.md from the 'Release Notes' section to the 'References' section, and moved the 'java-app-best-practices.md' file from the 'best-practices/' directory to the 'develop/' directory.
• Link Updates: Updated various internal and external links across several documentation files to reflect the new file paths and external URLs for release notes, ensuring all references are current and correct.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• TOC.md
  • Removed the 'Develop' guide section.
  • Removed the 'Best Practices' section.
  • Removed the 'Release Notes' section, including all historical release entries.
  • Moved 'TiDB Installation Packages' from the removed 'Release Notes' section to the 'References' section.
• backup-and-restore-use-cases-for-maintain.md
  • Updated the link to release notes from an internal path to an external URL.
• best-practices/java-app-best-practices.md
  • Renamed and moved to 'develop/java-app-best-practices.md'.
• br/backup-and-restore-use-cases.md
  • Updated the link to release notes from an internal path to an external URL.
• develop/dev-guide-connection-parameters.md
  • Updated the internal link for 'Best Practices for Developing Java Applications with TiDB' to its new path.
• develop/dev-guide-optimize-sql-best-practices.md
  • Updated the internal link for 'Best Practices for Developing Java Applications with TiDB' to its new path.
• performance-tuning-practices.md
  • Updated the internal link for 'Best Practices for Developing Java Applications with TiDB' to its new path.
• telemetry.md
  • Updated the link to release notes from an internal path to an external URL.
• upgrade-tidb-using-tiup.md
  • Updated the link to release notes from an internal path to an external URL.

Activity

• The author removed documentation entries for 'Develop', 'Best Practices', and 'Release Notes' from the Table of Contents.
• The 'TiDB Installation Packages' entry was moved from the 'Release Notes' category to the 'References' category.
• The 'java-app-best-practices.md' file was moved to the 'develop/' directory.
• Internal links in 'develop/dev-guide-connection-parameters.md', 'develop/dev-guide-optimize-sql-best-practices.md', and 'performance-tuning-practices.md' were updated to point to the new location of 'java-app-best-practices.md'.
• External links to release notes were updated in 'backup-and-restore-use-cases-for-maintain.md', 'br/backup-and-restore-use-cases.md', 'telemetry.md', and 'upgrade-tidb-using-tiup.md'.
• The changes are targeted for the 'master' branch.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request refactors the documentation for release-6.1 by removing the 'Develop', 'Best Practices', and 'Release Notes' sections from the table of contents. It also involves moving some files and updating internal links to maintain consistency. The changes align with the stated goals in the pull request description.

My review, guided by the repository's documentation style guide, focuses on improving the clarity and conciseness of the modified text. I've provided a few suggestions to make instructions more direct and sentences easier to parse. The link updates are correct and necessary given the structural changes.