Remove VERSION and stable.txt files

[RobertIndie]

Motivation

We currently have two hardcoded version files in place: VERSION which represents the current version and stable.txt which represents the current stable version. However, I'm curious about the intended function of these files. Are they merely for developers to conveniently reference the current and stable versions? And what is our approach to managing these files? For instance, how do we determine what constitutes a stable version? If there's no compelling reason to keep these files, I'd propose to remove them.

Please see more discussion here: https://lists.apache.org/thread/mrntb1y7ws173ohtdvz1v8q86pg50cn2

Modifications

• Remove VERSION and stable.txt files.

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.

Does this pull request potentially affect one of the following parts:

If yes was chosen, please highlight the changes

• Dependencies (does it add or upgrade a dependency): (yes / no)
• The public API: (yes / no)
• The schema: (yes / no / don't know)
• The default values of configurations: (yes / no)
• The wire protocol: (yes / no)

Documentation

• Does this pull request introduce a new feature? (yes / no)
• If yes, how is the feature documented? (not applicable / docs / GoDocs / not documented)
• If a feature is not applicable for documentation, explain why?
• If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

[BewareMyPower]

Could you resolve the conflicts?