Lina, can you be a bit more clear about what exactly you mean? It is not clear to me what exactly is being proposed. Do you mean in the URL, meaning we would not use /master/, but use /11/ or /11.0/ instead? Would the “master” URL not exist at all, would it redirect …? How will the branches be named? What is displayed in the version selector? Meaning will you also rename the branches or will you just redirect, e.g. “develop” to “11”, “stable” to “10”.
e.g. https://docs.typo3.org/m/typo3/reference-tca/**10.4**/en-us/
https://docs.typo3.org/m/typo3/reference-tca/**develop**/en-us/
I think before we start discussing it is important to know what exactly is being proposed.
It would also be good to know how this will impact the maintainance effort and how much effort it would be to change this.
Also, a number of suggestions have already been made in this area (see open issues and decisions). I believe I already made the suggestion to name each branch with explicit version (using only master - not master.minor as currently used, e.g. 11 instead of 11.0) and have a redirect from master to the version.
I agree that the word “master” is non intuitive for non-developers. It should however be intuitive for developers (although GitHub is already changing the default due to avoidance of terms “master”, “slave” etc.) - so it is really a problem since most of the documentation is for a technical audience. The current process corresponds to the core development repository and branching.