Docs: Simplifying Gutenberg versions table

[SirLouen]

I struggled for a long time to understand why a range of GB versions is being provided in the docs

https://developer.wordpress.org/block-editor/contributors/versions-in-wordpress/

This has caused confusion over time as people have tried to figure out how to best debug problems and report bugs appropriately.

It is still very confussing and keeps causing confusion (I know this because it has caused confussion to me, and all the members in the Test Team Training program I've been running through january also acknoledged when I asked)

The truth is that each Core version is locked to one single GB version, which happens to be the last one in the range. And all the versions in the range, were the ones being worked through during the alpha version which is correct, but also obvious and redundant (if you pushed the 19.3 for 6.7 its obvious that GB has been wroking from 19.4 to 20.4 for 6.8).

But for someone that simply wants to plainly understand which was the version locked in each core version for testing purposes for example, I believe that we should simply add the exact version that was pushed at that exact version.

I understand that for the core point releases can be even more confusing because its a cherrypicking process which means the last version + some cherry picked commits only (this is why I've added a paragraph explaining this)

In fact, to improve readabilty, I would even remove all the WP point versions from the list as they don't provide any value either to understand to correlation and go straight to the point.

For example

Gutenberg Version	WordPress version
21.9	6.9.X
20.4	6.8.X
19.3	6.7.X
...	...

And maybe leaving the versions before 5.1 just for reference on when this pattern changed.

[github-actions]

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Required label: Any label starting with [Type].
• Labels found: .

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: SirLouen <sirlouen@git.wordpress.org>
Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
Co-authored-by: juanmaguitar <juanmaguitar@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[Mamaduka]

In fact, to improve readabilty, I would even remove all the WP point versions from the list as they don't provide any value either to understand to correlation and go straight to the point.

100%. Using something like 6.8.x is a better approach. There's no point in releasing a version that shipped a completely different version of Gutenberg.

[Mamaduka]

Thanks, @SirLouen!

[SirLouen]

Thanks, @SirLouen!

I'm going to wait for @juanmaguitar double review also, because he has also been in the test program and we have been commenting on this.

[juanmaguitar]

I agree with this approach as it simplifies the view of GB versions included on each WP version and the maintenance of this table