Jun Ma

> > @freeznet thanks for adding the docs. I left several minor suggestions. Another concern is the historical doc versions you changed is 2.9.3 and 2.10.1 while the code PR...

Ping @Anonymitaet @urfreespace for review. This PR needs to work with #16938.

@BewareMyPower FYI - with this change implemented, you don't need to generate docs for the upcoming 2.8.4 release.

@Anonymitaet Thanks for your suggestions. > 1. How about not deleting 2.8.1/2.8.2/2.8.3/2.9.1/2.9.2/2.9.3/2.10.1 docs since there might be some occurrences referencing them? We can just not show them. Keeping these obsolete...

Hi @urfreespace, as @Anonymitaet suggested, if we add `deprecated` to the folders as a comprise to balance the confusion elimination and the potential external link issue, do you see any...

@Anonymitaet adding `deprecated` to those folders will change the URLs of doc pages, which also breaks the external references. If that's the case, I think I will also have to...

@Anonymitaet Yes, I talked with @urfreespace about the renaming today. @urfreespace Can you pls help confirm it to avoid any misunderstanding here?

Hi @tjiuming will you submit a doc PR as soon as this PR is approved and merged? Ping me if you need any review or other assistance.

> @momo-jun do you update all occurrences only for `master` or `master + other versions`? Master only. I want to verify whether they work well before applying the changes to...

@Anonymitaet the issue has been fixed and verified. I will find some time to update those links in versioned docs.