The generated version of the protobuf did not match the `.proto` file.
This caused issues when a new protobuf change was added

New properties are available to template developers.

Closes #1554

 * Added pod restart for ReplicaSet
 * Added --restart flag for helm CLI for upgrade/rollback commands
 * By default, restart is false

Closes #1511

satisfies #1326

 * Added pod restart for ReplicaSet
 * Added --restart flag for helm CLI for upgrade/rollback commands
 * By default, restart is false

Increases the default message size from 4MB to 10MB.

There are some places where releases are only located if they are in the
state DEPLOYED. That particular logic was incorrectly used for upgrades.
That caused #1566. While fixing that issue, I found that this was also
the root cause of #1587 (though because it was off by one). I added a
generic method to get the last release, regardless of its status.

This allows some behaviors that previously failed:

- 'helm upgrade' can now be performed on a DELETED release
- 'helm rollback' can now be performed on a DELETED release even if
  there is only one revision of that release history.

Closes #1566
Closes #1587

There were several places where an invalid name could be interpreted
into a wild-card by Kubernetes. That allows Bad Things.

This fix requires names to match the Kubernetes pattern for naming.

Closes #1594

This raises the limit from 14 to 53 chars based on the Kubernetes 1.4
name limit.

Closes #1528

When an install fails and --dry-run is set, return the broken YAML for
the user to debug.

Closes #1499

This does the following to improve deletion failure handling:

- In an UninstallRelease operation, the release is marked DELETED
  as soon as the basic checks are passed. This resolves 1508. I filed a
  followup issue for doing this even better when we can modify protos
  again.
- If a YAML manifest fails to parse, the error messages now suggests
  that the record is corrupt, and the resources must be manually
  deleted.
- If a resource is missing during deletion, the error messages now make
  it clear that an object was skipped, but that the deletion continued.

Closes #1508

closes: #1395

Correcting similar issue as the one with UpdateRelease
(#1137) for RollbackRelase

Handling release status updates on errors better
resolves #1137

When a deletion fails to remove a manifest file, the release should
still be marked as deleted. This changes the error handling to try to
delete all manifests, and then mark the release as deleted, then return
the errors.

Closes #1305

When `helm install -f foo.yaml bar` is called, and then the release is
upgraded with `helm upgrade happy-panda bar`, this will now re-use the
values that were submitted with `-f foo.yaml`. The same is true for
values specified with `--set`.

Closes #1227

closes #1244

This orders manifests both for installs and deletes so that the
manifests are ordered by kind.

Closes #1228

This feature allows you to rollback release to the
previous version of release.
resolves #1004