Hey All, Weekend was a bit more hectic than I thought it was going to be. There will be an 0.4 release this week.
Thanks, Paul On Feb 4, 2012, at 9:09 AM, Ramirez, Paul M (388J) wrote: > Hey Ricky, > > Awesome, every little bit helps. > > --Paul > > On Feb 3, 2012, at 10:57 AM, Nguyen, Ricky wrote: > >> OODT-341 is in progress. I wanted to address the comments Chris made >> (testing in Tomcat 5 and 6). Will try to get it done by 2/19.. >> >> On Feb 3, 2012, at 6:55 AM, Ramirez, Paul M (388J) wrote: >> >>> Hey Guys, >>> >>> So we all got busy but its now time to call her done and get stuff out the >>> door. Release candidate incoming on Feb 19th. Any objections? Please also >>> let me know what you are working on that you would like to get into 0.4. >>> Figure out if it can be included as is our you need to tie it up before >>> this timeframe. >>> >>> OODT-120 RADiX has filemgr, workflow manager, crawler, and opsui. Would >>> like to pull in PGE and integrate crawler and workflow manager a bit >>> better. That said it has some functionality now so we can tie off early if >>> need be. >>> >>> Chris I see your issues below and I know some have been worked where are we >>> at on OODT-215, 229, and 154. I see that 323 has been resolved. >>> >>> Anyone else have anything else sitting in Jira that they are planning on >>> getting done in this timeframe? >>> >>> The good news is there is a lot of stuff already done for this build so >>> pushing it out will help us get updates out to our community. >>> >>> Thanks, >>> Paul >>> >>> On Oct 5, 2011, at 6:36 PM, Mattmann, Chris A (388J) wrote: >>>> Paul, >>>> >>>> +1 for you to RM. I was originally intending to do it, but am happy to >>>> cede it to you >>>> in favor of spending my cycles wrapping up OODT-215. >>>> >>>> My issues I'd like to get wrapped up: >>>> >>>> OODT-215 -- Workflow 2 architecture >>>> OODT-229 -- Refactor all o.a.oodt.cas.filemgr.catalog.Catalog >>>> implementations and co-locate their shared code >>>> OODT-154 -- Flexible response handling for XMLPS >>>> OODT-323 -- Add new command line option in Workflow manager client to get >>>> Workflow Instance Metadata >>>> >>>> Cheers, >>>> Chris >>>> >>>> On Oct 5, 2011, at 9:32 AM, Ramirez, Paul M (388J) wrote: >>>> >>>> >>>>> Hey All, >>>>> >>>>> I think it would be great if we could get a 0.4 release out before >>>>> ApacheCon 2011. To accomplish this I would like to be able to roll a >>>>> release candidate on or before October 30th. There is already quite a few >>>>> issues closed for the release but I think we should push to get the >>>>> workflow updates in and the radix archetype finished off. I can commit >>>>> having the latter done in time. Is there anything else that we should try >>>>> to get into this release? If so, does the timeframe seem reasonable. If >>>>> not, lets discuss and consider whether items can be pushed to 0.5. I >>>>> think it would be a big win for us to get a 0.4 release out in time for >>>>> ApacheCon. >>>>> >>>>> Thanks, >>>>> Paul Ramirez >>>> >>>> >>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>> 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 >>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>> >>> >> >> >> >> >> --------------------------------------------------------------------- >> CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, >> is for the sole use of the intended recipient(s) and may contain confidential >> or legally privileged information. Any unauthorized review, use, disclosure >> or distribution is prohibited. If you are not the intended recipient, please >> contact the sender by reply e-mail and destroy all copies of this original >> message. >> >> --------------------------------------------------------------------- >> >
