anchor.diff:  reference as you add elements to the release.
   
   Go through any scripts you have created and note the files cited by each script.
  +_note package path_ and _go through all job templates_.
   The names of these files must be added to the `packages` block of the job spec.
   In our example, they are `ardo_web` and `ruby_1.9.3`.
   
  
positive.code: 1. Create a **final release**.
    * BOSH bumps the release number by whole number.
  
  Beside the workflow, this tutorial explains principles to
  keep in mind when creating BOSH releases:
  
  * BOSH releases package up all dependencies.
  * BOSH releases do not add blobs to a git repository.
  * BOSH releases remain buildable for a long time.
  * BOSH releases do not necessarily depend on the internet.
  
  * Using underscores in filenames is the BOSH way.
  * Commenting your code to facilitate debugging is the BOSH way.
  
  ## <a id="..."></a> Decide What to Release ##
  
  Some releases contain a single app.
  Others are collections of the pieces of software that together form a particular service.
  For example, such a collection might include a few MySQL nodes along with a dashboard app.
  You might think of each of these pieces of software as an area of functionality, or a feature.
  In a BOSH release, each such piece is a _job_.
  
  In a BOSH release:
  
  * **jobs** describe pieces of a service.
  * **packages** provide source code and dependencies to jobs.
  * **src** provides non-binary files to packages.
  * **blobs** provides binaries not checked into a Git repository.
  
  Creating a release entails several judgment calls: what to include, how to structure it, and how to split up jobs and packages.
  
  
negative.code: 6 directories, 1 file
  </pre>
  
  **Note**: The release directory is where you run all the BOSH commands in this tutorial.
  
  ## <a id="..."></a> Create the Job Skeletons ##
  
  For each piece of software you include in a release, you create a job.
  
  When first created, the job is a _skeleton_: an empty structure to be filled up
  as release creation progresses.
  
  The example release only includes one job.
  