Clarify that current version 11 is 10.2

postponing this as I don't believe we can make experimental modules part of the standard install.

But you are correct that 11.x is 10.2

Looking at it as 11.x being a master branch and all releases will just be a tag off it.

Thanks for a fast response @smustgrave. That's also what I thought, but in this case it's a bit of an extraordinary situation, perhaps calling for unusual measures.

Under all circumstances, the new branching scheme is a good move, and will simplify many things, preventing lots of updating of versions, making searching issues easier, etc.

📌 Add a branch alias for 11.x Fixed might help here.

With Drupal 11 targeted for this year, I think its getting real close that the dev version of Drupal 11 will actually be Drupal 11, so I think we avoided this problem for long enough to be able to close it? Sorry for the irony :)

Looking forward to Drupal 11 :) Has the "real" standalone 11.x dev-version been released yet, or is it close?

Any day now, any day now :)

... it shall be released :)

So now 11.x is actually 11.x :) https://www.drupal.org/about/core/blog/drupal-11-is-now-open-for-develop... →

Perfect, thanks @Gábor Hojtsy!

Should the text on https://www.drupal.org/project/drupal/releases/11.x-dev → be updated and the mention that it is a temporary measure and no release will ever be tagged be removed, or perhaps a https://www.drupal.org/project/drupal/releases/11.0.x-dev → will be created eventually?

Yeah a 11.0.x will be created when 11.0.x diverges from the future 11.1.x (which is initially done on 11.x as well). Basically 11.x is "main" but many d.o tools can't handle a number-less branch, so we did not name it main.