ShardingSphere release approach

[vikiuvb]

I noticed that the community has been adding a lot of useful features in ShardingSphere recently. So, kudos to the community.

One observation I have is there have been a lot of backward incompatible changes done in ShardingSphere, particularly on the DistSQL syntax.

For instances,

• ADD RESOURCE have been changed to REGISTER STORAGE UNIT.
• The HINT SQL comment format has been changed.

What is the approach are we taking? Are we trying to move fast and break things? As the project matures, this approach can soon become challenging for adopters as they might have to frequently change the tools to adopt to the new syntax changes.

Also, it looks like we are not following the SemVer release format. For any backward incompatible change, I believe we should have changed the major version rather than the minor version (Ex: 5.2.0 to 5.3.0). It gives a false impression to the adopters that the new version is fully backward compatible with the existing version, whereas in reality it breaks.

[RaigorJiang]

Hi @vikiuvb ,
Thank you for your attention and suggestions!

Indeed, 5.3.0 brings a lot of changes, including DistSQL, Spring dependencies, etc.
DistSQL is still young for ShardingSphere, and it is still in the stage of rapid adjustment. The purpose of changing the API is to provide more compatibility forward and reduce frequent adjustments in the future.

We will try our best to make the API stable, and hope you like this community, thanks you!