Proposal: Need a release strategy

[adamqqqplay]

Many mature open source projects have their own release strategies. They announce the date of version release and the cycle of development and maintenance in advance, which will bring many benefits to users and developers. Typical cases such as golang, Kubernetes and Kata Containers.

There seems to be some confusion about the current release strategy for the Nydus project, either this repo or the nydus-snapshotter repo. Although we may not be able to reach the release mode of a mature project overnight, there are some things we can do, such as:

1. Follow the definition of Semantic Versioning to maintain certain compatibility.
2. Announce freeze and release dates for the next version weeks in advance in the docs or Wiki.
3. Manage issues that need to be resolved before release through projects and milestone.
4. Detailed description of major API changes and upcoming deprecated features in the release log.

From my point of view, such a strategy is conducive to the long-term development of Nydus project. If you have any comments or suggestions, please leave a comment. Thanks!