It is now possible to create plugins with chart download capabilities for custom, non-http protocols.
Furthermore it is possible to reuse helm packages to implement alternative clients with these custom downloader functions.

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.

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

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.

Trigger deployment as success when new replicaSet has reached minimum you need which is number of replicas minus maxUnavailable

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

closes: #1985

Fix codefences and nits in charts.md. Correct whitespace in charts. Add clarity to description of ImportValues requirements field.

Slightly reorganized and retitled to be accurate.

Closes #2097

The WordPress community and especially the WordPress foundation
strongly prefer the use of WordPress, with the capital P.

The old link is invalid (404)

The behavior of how the `--wait` flag interacts with the hook lifecycle
was not documented. This adds clarification on the lifecycle behavior
with the `--wait` flag.

fixing typo

Adds the `required` function in enginge.go to support required
properties in values.yml. When a chart developer wishes to specify
intent in requiring a value, they can use this function to declare
an error message that gets returned when chart rendering fails
when a required value is not present in values.yml.

Closes #1580

This provides a simple field to expose the version of the application
contained in a chart.

Closes #2036

This adds a basic Chart Best Practices guide.

Closes #1993

$.Template.basePath already contains "templates/"