anchor.diff:  
   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
  -* Do a new dev release and then bosh deploy to see that new release succeeds deploying.
  -* You can use `bosh deploy --recreate` to deploy all VMs from scratch.
  +In general, it helps to open a separate terminal and log in on the job VM, and
  +observe logging output as you test your release.
  +
  +If your release fails tests, follow this pattern.
  +
  +* Fix the code.
  +* Do a new dev release.
  +* Run `bosh deploy` to see whether the new release deploys successfully.
  +
  +Using `bosh deploy --recreate` can provide a clearer picture because with that option,
  +BOSH deploys all the VMs from scratch.
   
   ## <a id="final-release"></a> Do a Final Release  ##
   
  
positive.code: When creating dev releases, do not run `bosh upload blobs`.
  That command is discussed below, in connection with final releases.
  
  ## <a id="..."></a> Update Specs to Complete Jobs ##
  
  _what have we not done yet?_
  
  ## <a id="create-props"></a> Create Job Properties  ##
  
  You can specify what in your service is configurable at deployment time.
  Each configurable input or control is a _property_ that belongs to a
  particular job.
  
  Creating properties requires three steps:
  
  
negative.code: 
  Now you can upload your blobs to a blobstore:
  
    `bosh upload blobs`
  
  ### <a id="final-commit"></a> Commit ###
  
  