anchor.diff:  
   When creating a release, you likely use a source code repository.
   But releases often use tar files or other binaries, also known as blobs.
  -Checking blobs into a repository may be problematic if the repository you use
  -is not well-suited to dealing with large binaries.
  -(Git, for example, is not.)
  +Checking blobs into a repository is problematic if your repository
  +unsuited to dealing with large binaries (as is true of Git, for example).
   
   BOSH lets you avoid checking blobs into a repository by doing the following:
   
  
positive.code: VM creation in BOSH works on consistent principles that are important to know
  when you debug a release:
  
  * Compilation VMs are newly created every time you deploy.
  
  * Job VMs are newly created in two cases: the first time you deploy a release,
  and every time that you deploy using the `--recreate` option.
  
  ### <a id="what"></a> Decide What to Release ###
  
negative.code: #### <a id="runtime"> </a>Identify runtime dependencies ####
  
  Whenever a control script or other template cites a package name, the job
  that the template belongs to depends on the cited package at runtime.
  
  For each job, find all the cases where your control scripts cite packages.
  Add these runtime dependencies to your dependency graph.
  