Drupal semantic versioning for modules— 2.0.x or 2.x branch?

Near as i can tell, Drupal.org wants to allow us to simply use a 2.x branch and make releases for 2.0.0, 2.1.0, 2.2.1394 and all that, but Drupal.org infrastructure just does not support it well yet.

Drupal itself wants to only use ‘main’ but is trying to use ‘11.x’ (whereas previously it always had to be ‘10.0.x’, ‘10.1.x’, etc.) so maybe this is getting closer.

To be clear, when i say “support it well” i mean that a person visiting the project page can easily see the latest point release and the development branch that it came from, and click through to the development branch page to get the composer command for using that if they want to ride the wave with the maintainer.

And that’s what is just not working with a “2.x” branch instead of a “2.0.x” branch, and that’s pretty annoying.

Resources and discussions relevant to semantic versioning in Drupal generally: