Release instruction is needed.

[Random-Liu]

Forked from #63 (comment).
We need a release instruction to standardize the release process. The release instruction should cover:

• How to build release packages
  • Build docker image.
  • Build tar ball for standalone.
  • ...
• How to cut release
  • Version a release
  • Update CHANGELOG.md
  • Create branch/tag
  • Create github release.
  • ...
• How to update kubernetes
  • Update e2e test
  • Update addon pods in cluster
  • ...

This has relatively lower priority than the features, will file the doc before cutting release.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close