[skip ci] Create SUPPORT.md and RELEASE.md (#950)

* [skip ci] Create SUPPORT.md

* [skip ci] Create RELEASE.md

RELEASE.md

+# Milvus Release Methodology and Criterias
+
+## Release methodology
+
+Milvus releases are packages that have been approved for general public release, with varying degrees of caveat regarding their perceived quality or potential for change. 
+They are stable releases intended for everyday usage by developers and non-developers.
+
+Project versioning follows the specification of [Semantic Versioning 2.0.0](https://semver.org/).
+
+## Release criteria
+
+- Milvus core test code coverage must be at least 90%.
+- Reported bugs should not have any critical issues.
+- All bugs, new features, enhancements must be tested.
+- All documents need to be reviewed with no broken link.
+- Pressure testing, stability testing, accuracy testing and performance testing results should be evaluated.
+

SUPPORT.md

+# Support for deploying and using Milvus
+
+We use GitHub for tracking bugs and feature requests. If you need any support for using Milvus, please refer to the following resources below.
+
+## Documentation
+- [User Documentation](https://www.milvus.io/docs/guides/get_started/install_milvus/install_milvus.md)
+- [Troubleshooting Guide](https://www.milvus.io/docs/v0.6.0/guides/troubleshoot.md)
+- [FAQ](https://www.milvus.io/docs/v0.6.0/faq/operational_faq.md)
+
+## Real-time chat
+[Slack](https://join.slack.com/t/milvusio/shared_invite/enQtNzY1OTQ0NDI3NjMzLWNmYmM1NmNjOTQ5MGI5NDhhYmRhMGU5M2NhNzhhMDMzY2MzNDdlYjM5ODQ5MmE3ODFlYzU3YjJkNmVlNDQ2ZTk): The #general channel is the place where people offer support.
+
+## Other
+[Bootcamp](https://github.com/milvus-io/bootcamp): It provides more scenario-based applications and demos of Milvus.