new release for stopped services

[pschrammel]

hi, could you do an "official" docker release with the #16 patch?
thx

[smazurov]

Hey, I will be sunsetting this service as rancher's cron service is superior implementation (Imo). My reasons:

• Official cron only depends on a local docker engine connection. This one depends on Rancher/Metadata apis. This means if you're updating rancher or its unavailable for whatever reason, official one keeps working, as long as the machine/docker on it keeps working.
• Much less impact from failure. If the machine hosting this service goes down, all your env's cron jobs are paused until container can be rescheduled.

Migration should be as simple as adding the official cron service, changing the label of your cron'd service and verifying it works.

Unless there is a huge reason that I am missing, I do not see a reason to continue this project.