Hey Guys,

I am nearing completion on OODT-215 [1]. Yes, for real. Check this out:

http://minus.com/moumqrviB/

I even drew a picture to illustrate. Basically everything in yellow I've 
implemented.
That diagram in many ways constitutes most of the new contributions of Workflow2
that are still on the critical path. The best part? All of that yellow code is 
unit tested
and tests are passing every night on our Jenkins server. The things left to 
implement
are basically:

1. Wire up the RunnerThread to periodically poll the TaskQuerier for the next 
Task in the
list of Runnable, Prioritized and sorted tasks to execute (that is constantly 
being re-prioritzed).
2. Hand that task off to the Workflow Runner framework for execution.
3. Finish tying the State model to the new Workflow Processor framework in 
place. 

Yes, not lying, that's pretty much it. If I can get 1-3 working, we're 
basically in business
for Workflow2. I will also at that point quickly whip up a back compat layer so 
that 
the old Workflow engine model (ThreadPoolWorkflowEngine) will still work, but 
I'm really shooting to wrap up OODT-215 this week and get 0.4 out the door.

So, please, all, if you can, help me get there. When I throw something up on 
ReviewBoard
and/or anything else, I'd appreciate your help and eyes. And if you actually 
understood
what I said above and can contribute, would love it anywhere and any place. 
Thanks!

Paul, I assume you can roll the 0.4 RC this weekend?? :) For real this time.

Cheers,
Chris

[1] https://issues.apache.org/jira/browse/OODT-215 

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattm...@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Reply via email to