chartutil create ingress example

clarify helm serve's intent

fix(tiller): ignore empty YAML documents during delete

A lot of community members are looking at `helm serve` as a production webserver to host their
charts. There are much better solutions out there like s3, wabs or gcs for cloud storage and
nginx, haproxy or apache for DIY dedicated web servers. Steering users in the right direction
will help users make the right decision when it comes to serving their charts in production.

Closes #2256

fix(helm): fix nil pointer in requirements.go

fix(scripts): don't include plugins for generating docs

docs(*): Add ci script to confirm docs are up to date with commits

This fixes a segfault that was the result of assigning to a property of
a nil pointer.

Closes #2244

* tiller_fix_2261

* fix(tiller) 2261 Increase maxMsgSize to 20MB

fix(helm): correct import for apps api

* cleanup named imports

ref(*): kubernetes v1.6

feat(tiller): support version constraint on chart

fix(helm): remove duplicate commands

docs(related): add note about helm-plugin GitHub tag

Rebase on kubernetes v1.6

fix(init): use ImagePullPolicy Always for canary installs

fixes: #2155

Added release-name to helm delete error

Fixes https://github.com/kubernetes/helm/issues/2251
In case a user tries to delete a non-existent release,
the error message displayed was missing release-name.

Add note about gopath in developer docs

Fixes hard-coded linux based file-separator

Fixes https://github.com/kubernetes/helm/issues/2254

Added a note that helm needs to be in a
specific directory path in order for it
to be compiled.

ref(plugin): cleanup unused functions

Replaced InstallRelease with InstallReleaseFromChart in cmd/install.go

Fixes https://github.com/kubernetes/helm/issues/2240

`helm install` command was calling chartutil.Load twice,
once from `run` method and
another time from `client.InstallRelease` which is called from `run` method in `cmd/helm/install.go`

Closes #2238

docs(*): Adds developer workflow documentation

This adds documentation for the developer workflow as approved in #2069

Closes #2069

This provides the Chart.yaml field `tillerVersion`, which is a semver
range. It allows users to choose to constrain a chart to a specific
version.

The reason for this is that we keep introducing new template functions,
but we have no way of saying "this chart will only work with Tiller
newer than...".

The check on version is _only_ done on Tiller. The client does not check
at all, since it does not do any template expansion on its own.