That's fine - but someone has to be the first :P -g On 11/4/2013 8:57 AM, Mundy, Michael B. (Mike) wrote:

I'll wait for the major build in a few weeks to make the switch to the user_and_job_state service.

Tom, please deploy CBD from what is currently in the master branch.

Mike Mundy | Senior Analyst Programmer | Bioinformatics Systems Unit | 507-266-7232 | [email protected] Mayo Clinic | 200 First Street SW | Rochester, MN 55905 | mayoclinic.org <http://www.mayoclinic.org>

On 11/4/13 10:50 AM, "Gavin Price"<[email protected]> wrote:

...

I'd say the question is whether you're ok being an early adopter of an immature service - if you're ok with that I am as well.

One minor point - I made a small change to the API of the list_jobs function on Friday. I'd imagine you're not using that function, but if you are you'll need to update.

-g

On 11/4/2013 6:34 AM, Mundy, Michael B. (Mike) wrote:

...

Yes, I would like a new deploy of the CBD service. Gavin, are you OK with switching CBD to use the user_and_job_state service? I have the changes in a branch that I would need to merge to master before a deploy.

Mike Mundy | Senior Analyst Programmer | Bioinformatics Systems Unit | 507-266-7232 | [email protected] Mayo Clinic | 200 First Street SW | Rochester, MN 55905 | mayoclinic.org <http://www.mayoclinic.org>

On 11/1/13 2:04 PM, "Thomas Brettin"<[email protected]> wrote:

...

Gavin is asking for a production release of the user_and_job_state service. A production deploy of the handle_service would also be good. The may guys also want the CBD module deployed to prod. Can we start this up Monday morning?

There may be others as well.

Tom