Why have we shipped two different versions of content-editor so far?

6.2 still ships with content-editor v1 by default (in dx-core-webapp), because upgrading to v2 is not directly compatible (change of data structure, hence required changes in project templates), only the demo-webapp bumps it to v2

Foundation suggestion

• having two versions of the same module at the same time in 6.2.x dx-core webapp is a corner case that the release bot doesn't support, requiring manual involvement, which we want to avoid
• 6.3.0's release is a rare opportunity to do a breaking change
• 6.2 dx-core webapp bundles content-editor v1 and then the 6.2 demo webapp showcases content-editor v2. When 6.3 comes out, we could ship content-editor v1 exclusively with 6.2.x (DXC and demo), v2 with 6.3.x (DXC and demo)
  • making it all simpler
  • improving release automation
  • keeping the possibility to showcase content-editor v2 (with 6.3.x)
  • keeping 6.2.x unchanged (content-editor v1 officially supported baseline)