Promoting j2cl/GWT3/?

[xamde]

As a follow-up to the discussion on gitter, I would like to agree on a common goal for the future of GWT and jc2l with regards to features and branding.

Summary of our situation:
As I understood, there are "legacy" GWT apps out there, which should continue to run and evolve. They need a clear, hopefully not too bumpy migration path.
If you guys with all the knowledge on GWT and j2cl would start fresh today, you would choose j2cl, as it is the more modern compiler and used in-house at Google. So many GWT features would be left out, most notably the built-in GWT widget system.

My opinion
As a developer, I am eager to migrate to the modern j2cl stack. I would love a clearly documented homepage for this, which does not describe any GWT legacy features.
GWT 2.x is the current active version.
I would prefer to use a small, well documented GWT-j2cl-minimal version over a large GWT 3.x.
I guess we really have the use-cases on-boarding and maintenance.
For on-boarding we need a coherent message, tooling, samples .. and some naming to describe it.

Maybe GWT 3.x could be the step to a version based on j2cl, but backwards-compatible in some areas.
GWT 4 could be the fresh new pure j2cl way, in which the former GWT features become pure libraries and all extra stuff like GWT modules files and whatnot are not longer supported.
GWT 3 and GWT 4 would share the same j2cl-base core.
We would keep the popular GWT branding.

What are your opinions on naming the pure j2cl approach (for newbies) vs. the GWT 2.x approach (for code evolution)?