ChangeLog.md in bosh-cloudfoundry-0.7.1 vs ChangeLog.md in bosh-cloudfoundry-0.7.2

- old
+ new

@@ -18,7 +18,8 @@ * templates are versioned for each final release (unless new templates not required for new release) * different sizes of deployments (orders of magnitude), such as small, medium & large: `bosh create cf --deployment-size large` * mutable/changable properties (and immutable properties) for each template version: `bosh change cf attributes persistent_disk=8192` * can initially use public http://xip.io for DNS and change to custom DNS later: `bosh change cf attributes dns=cf.mycloud.com` * v141 cf release & template fixes [v0.7.1] +* bosh stemcells now have cpi/hypervisor in name [v0.7.2] The latter means that new versions of this rubygem can be published that are backwards compatible with aging deployments of Cloud Foundry. There should not be any forced coupling of old `bosh-cloudfoundry` to old `cf-release` final releases.