Release procedures

    1. Test everything twice on Docker image and .
    2. Send a pull request that increases version numbers in all files. Follow versioning guidelines. Files to keep in sync are listed below:
      • aio/gulp/conf.js
      • YAML files from aio/deploy
      • Helm Chart from aio/deploy/helm-chart/kubernetes-dashboard: image.tag of and values.yaml, version and appVersion of Chart.yaml
    3. Get the pull request reviewed and merged.
    4. Create a git release tag for the merged pull request. Release description should include a changelog.
    5. Update addon config in the repository.
    6. Update addon config in the kops repository.
    7. Release Helm Chart by running the aio/scripts/helm-release-chart.sh script from the newly created git tag, then push the git branch of your https://github.com/kubernetes/dashboard/ git remote.

    Official release procedures are done by CI after successful TAG build automatically, that are pushed to repositories.

    1. Increment MAJOR when there are breaking changes that affect user’s workflows or the UX gets major redesign.
    2. Increment MINOR when new functionality is added or there are minor UX changes.

    Versions 0.X.Y are reserved for initial development and may not strictly follow the guidelines.

    Development releases

    On every successful master build CI provides development releases, that are pushed to repositories. Each build produces one image for each architecture. The images are tagged with head.