fix(glide.yaml): update SemVer to 1.2.3

fix(*): add missing proto for weight hook

Separate manifests printed by "helm init" with YAML document boundary markers

There was a bug in SemVer 1.2.2 that miscalculated a couple of
comparison patterns.

Add more object kinds to sorted installation order

feat(helm): add support for repo alias

feat(hooks): Adds weighted hooks

feat(helm): add --reuse-values flag to upgrade

This makes it possible to re-use the existing values on an upgrade,
merging in any new values set by `-f` or `--set`.

Closes #1876

docs(related): Added podcast, plugin article

fix(helm): manifests string parsing works for newlines in the manifests

support repo alias in requirements.yaml
The syntax should be like: "alias:reponame" or "@reponame".

closes: #1985

fix(tiller): fix helm status failure on missing resource

fix(helm): add --destination flag to 'helm package'

Fixes TestInstallRelease_VerifyOptions & TestUpdateRelease_VerifyOptions

Fix identation of `helm dep` help text

In order to allow the stream emitted by "helm init --debug" to be fed
back into "kubectl create/apply -f", use YAML starting and ending
document boundary markers instead of blank lines to separate the
individual manifests.

The `repository` lines in the help text for `helm dep` were misaligned
with the rest of the dependency block.

Following tests were failing unnoticed
- [ ] TestUpdateRelease_VerifyOptions
- [ ] TestUpdateRelease_VerifyOptions

Fixed those tests for the reason of failure.
Also added error checking to rest of the tests in same test-file,
so that new failures do not un-noticed.

The following kinds are newly addressed:

  CronJob
  LimitRange
  ReplicaSet
  ResourceQuota
  StatefulSet

Furthermore, adjust the installation and uninstallation order to
better respect likely dependencies. Bare pods remain a difficult one
to place properly in both sequences.

Sort dependent RBAC role and binding kinds during installation and uninstallation

able to build without being in a git repository

fix(helm): local path in requirements.yaml relative to working dir

During installation and uninstallation, handle the RBAC-related
ClusterRole, ClusterRoleBinding, Role, and RoleBinding kinds in an
order that respects their potential referential integrity, namely that
ClusterRoleBindings can refer to ClusterRoles and ServiceAccounts, and
RoleBindings can refer to ClusterRoles, Roles, and ServiceAccounts.

Fixes #2199.

closes bug: 2103

fix(helm): Don't assume index.yaml is sorted

fix(tiller): adding kind to tiller client logs

Fix typo in chart guide

Closes #2162