anchor.diff:  As a matter of principle, BOSH releases:
   
   * Package up all dependencies.
  -* Do not add blobs to a git repository.
   * Remain buildable for a long time.
  -* Do not necessarily depend on the internet.
  +* Avoid adding blobs to a git repository.
  +* Avoid depending on the internet.
   
   As a matter of good practice, when creating BOSH releases, you should:
   
  
positive.code: 
     `bosh upload release`
  
  ## <a id="..."></a> Test the Dev Release  ##
  
  What tests to run depends on the software you are releasing.
  
  
  
  * Debug primer: log in on VM, etc.
  * If your release fails any of these tests, fix and do a new dev release.
  
  ## <a id="..."></a> Do a Final Release  ##
  
  
negative.code:   ctl.erb: bin/ctl
  
  packages:
  - bg_worker
  
  ~~~
  
  **Note**: The file paths that you provide for templates are relative to
  what is in effect a home directory for the job on the VM:
  
  ~~~
  /var/vcap/jobs/<job_name>/
  ~~~
  
  For example, the path we provided for the `bg_worker` control script was
  `bin/ctl`.
  BOSH translates that into the full path `/var/vcap/jobs/bg_worker/bin/ctl`.
  
  ### <a id="commit-one"></a> Commit ###
  
  You have now created one or more job skeletons; this is a good time to commit.
  
  Be aware that if you followed the recommended practice of using the `--git` option with
  `bosh init release`, the correct `.gitignore` file has been automatically created for you.
  
  ### <a id="strategy"></a> A note about work strategy ###
  
  You are about to begin four central parts of the tutorial,
  Make Dependency Graphs, Create Packages, Add Blobs Locally, and Update Specs to Complete Jobs.
  You can go one section at a time, completing one section for all jobs,
  doing the same for in the next section, and so on.
  Alternatively, you can go one job at a time, completing all four sections for one job,
  doing the same for the next job, and so on.
  
  For releases with just a few jobs, going one section at a time is probably easiest.
  That is what we'll do in this tutorial.
  If you have a larger number of jobs, going one job at a time may be more efficient.
  Choose the approach that seems most comfortable and least error-prone.
  
  ## <a id="graph"></a> Make Dependency Graphs ##
  
  There are two kinds of dependencies in a BOSH release:
  
  * The **runtime dependency**, where a job depends on a package at runtime.
  For example, the `web_ui` job depends on Ruby.
  * The **compile-time dependency**, where a package depends on another package at compile time.
  For example, Ruby depends on the YAML library.
  
  