anchor.diff:  title: Creating a BOSH Release
   ---
   
  -The iterative workflow for creating BOSH releases looks like this:
  +The workflow for creating BOSH releases is iterative, and looks like this:
   
     <%= image_tag("release-iterate.png") %>
   
  -The notion of the **dev release** and the **final release** is built into
  -the way BOSH automatically numbers releases.
  -
  -We can make this clear by describing the iterative workflow in words:
  +A more detailed description of the workflow reveals how,
  +as you iterate, BOSH automatically numbers your releases:
   
   1. Develop or modify the application.
   1. Create a **dev release**.
  
positive.code:   ctl.erb: bin/ctl
  
  packages:
  - ardo_web
  
  ~~~
  
  ### <a id="..."></a> Commit ###
  
  You have now created a job skeleton.
  If your release includes several jobs, go back and repeat this process for each one.
  
  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="..."></a> Make a dependency graph ##
  
  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 `ardo_web` 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.
  
  
negative.code: BOSH asks for release name.
  For a dev release, this can be anything.
  
  ### <a id="..."></a> Deploy the Dev Release  ###
  
  Target a director.
  
  