---
2.0.0:
  - deletion of running jobs is now prohibited (silently ignored actually).  rq
    has no central process and no communication whatsoever is done between
    nodes.  because of this it is not possible for delettion of a running job
    from the queue to somehow be signaled to the possibly remote node.  however,
    it is NEVER an error to kill a job on some host - rq will simply report the
    failed exit_status - thus one can easily set up a simple command, perhaps
    using ssh keys, to kill a remote job and THEN delete it from the queue if
    this behaviour is truely needed.  in simple terms a job may be removed from
    the queue BEFORE it starts running or AFTER is finishes - no matter what the
    exit_status.
  - when submitting a runner(s) can be specified.  feeders respect this
    'request' and only feeders whose hostname matches the list will run the job.
    eg.  jobs may be submitted to a specific host.
  - submitted jobs can now marked restartable (--restartable).  feeders respect
    this and restart any jobs found dead when starting - this means a node
    running a job can be rebooted mid-job and the job will restart when the
    feeder starts again.
  - fixed bug with pidfile generation on machines sharing the same home
    directory via NFS - big thanks to David Desmarest.
  - status reporting has been augmented and now includes some rough metrics for
    the cluster
1.1.0:
  - some refactoring on all the MainHelpers
  - added rotate mode
1.0.0:
  - bug fixed where 42 un