<commit_before># Release Process

The following steps must be done from a Linux x64 bit machine.

- Do a global replacement of tags so that docs point to the next release.
- Push changes to the release-x branch and apply new tag.
- Push all the changes to remote repo.
- Now, first build all the binaries:
```sh
$ cd ~/go/src/github.com/appscode/searchlight
$ ./hack/make.py build; env APPSCODE_ENV=prod ./hack/make.py release; ./hack/make.py push
```
- Build and push searchlight docker image
```sh
./hack/docker/searchlight/setup.sh; env APPSCODE_ENV=prod ./hack/docker/searchlight/setup.sh release
```
- Build and push both forms of icinga image:
```sh
./hack/docker/icinga/build.sh; ./hack/docker/icinga/build.sh release
./hack/docker/icinga/setup.sh; ./hack/docker/icinga/setup.sh release
```
- Now, update the release notes in Github. See previous release notes to get an idea what to include there.


Now, you should probably also release a new version of kubed. These steps are:
- Revendor kubed so that new changes become available.
- Build kubed. Add any flags if needed.
- Push changes to release branch.
- Build and release kubed docker image.
- Now update Kubernetes salt stack files so that the new kubed image is used.<commit_msg>Fix binary release command<commit_after># Release Process

The following steps must be done from a Linux x64 bit machine.

- Do a global replacement of tags so that docs point to the next release.
- Push changes to the release-x branch and apply new tag.
- Push all the changes to remote repo.
- Now, first build all the binaries:
```sh
$ cd ~/go/src/github.com/appscode/searchlight
$ ./hack/make.py build; env APPSCODE_ENV=prod ./hack/make.py push; ./hack/make.py push
```
- Build and push searchlight docker image
```sh
./hack/docker/searchlight/setup.sh; env APPSCODE_ENV=prod ./hack/docker/searchlight/setup.sh release
```
- Build and push both forms of icinga image:
```sh
./hack/docker/icinga/build.sh; ./hack/docker/icinga/build.sh release
./hack/docker/icinga/setup.sh; ./hack/docker/icinga/setup.sh release
```
- Now, update the release notes in Github. See previous release notes to get an idea what to include there.


Now, you should probably also release a new version of kubed. These steps are:
- Revendor kubed so that new changes become available.
- Build kubed. Add any flags if needed.
- Push changes to release branch.
- Build and release kubed docker image.
- Now update Kubernetes salt stack files so that the new kubed image is used.
{'fraction_non_alphanumeric': 0.0944, 'fraction_numerical': 0.0016, 'mean_word_length': 3.718867924528302, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4990539', 'n_tokens_mistral': 791, 'n_tokens_neox': 746, 'n_words': 328}