I've set up a build for the new branch. https://builds.apache.org/view/M-R/view/OODT/job/oodt-avro-rpc/ I'm taking responsibility of keeping it up to date with trunk until we are ready to merge into trunk. Thanks Lewis
On Wed, Sep 2, 2015 at 10:52 PM, Lewis John Mcgibbney < [email protected]> wrote: > Hi Tom, > No probs I'll follow up here when I'm done merging it all in. There is > quite a bit of code :0| ;) > Anyways folks, the new branching activity is ongoing at > http://svn.apache.org/repos/asf/oodt/branches/avro_rpc/ > I'll follow up here once we are done with it, we can then get some serious > testing done. > By the way, just for heads up. In 0.11-SNAPSHOT we intend to mark > hopefully all of the XMLRPC work as @Deprecated. In 0.12 we will then > progress with phasing it out entirely and replacing it with the AvroRPC > implementation. By then we will have it well tested and will have built > confidence in it all. > Thanks > Lewis > > On Mon, Aug 31, 2015 at 1:29 PM, Tom Barber <[email protected]> > wrote: > >> Let me know when you've got stuff sorted Lewis, I'm happy to be a >> XMLRPC-less File Manager guinea pig. >> >> Tom >> >> On Mon, Aug 31, 2015 at 9:09 PM, Lewis John Mcgibbney < >> [email protected]> wrote: >> >> > ACK >> > Will do this shortly Chris. >> > Thanks >> > >> > >> > On Mon, Aug 31, 2015 at 12:58 PM, Mattmann, Chris A (3980) < >> > [email protected]> wrote: >> > >> > > +1 from me to push this up into a branch. >> > > >> > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> > > Chris Mattmann, Ph.D. >> > > Chief Architect >> > > Instrument Software and Science Data Systems Section (398) >> > > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >> > > Office: 168-519, Mailstop: 168-527 >> > > Email: [email protected] >> > > WWW: http://sunset.usc.edu/~mattmann/ >> > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> > > Adjunct Associate Professor, Computer Science Department >> > > University of Southern California, Los Angeles, CA 90089 USA >> > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> > > >> > > >> > > >> > > >> > > >> > > -----Original Message----- >> > > From: Lewis John Mcgibbney <[email protected]> >> > > Reply-To: "[email protected]" <[email protected]> >> > > Date: Thursday, August 27, 2015 at 4:35 PM >> > > To: "[email protected]" <[email protected]> >> > > Subject: Re: Strategy for Closing off GSoC 2015 Work >> > > >> > > >I'm thinking that we branch trunk and integrate the code (once we >> rebase >> > > >properly and compile a list of TODO's) into the branch. >> > > >I'll be happy to ensure that the branch stays up to date with trunk. >> > > >This way we can test, stabilize and build confidence in the new >> remote >> > > >procedure implementations for various modules. >> > > >We also still need to build it in to radix so that is a major step as >> > > >well. >> > > >Any objections to branching trunk post 0.10 release? >> > > > >> > > >On Tuesday, August 25, 2015, Tom Barber <[email protected]> >> > wrote: >> > > > >> > > >> Yeah I'm well up for getting this all complete xmlrpc in osgi is >> > giving >> > > >>me >> > > >> a rash. >> > > >> >> > > >> The stuff I'm developing I'll happily skip xmlrpc direct to avro if >> > it's >> > > >> functional. >> > > >> >> > > >> Tom >> > > >> On 25 Aug 2015 07:58, "Chris Mattmann" <[email protected] >> > > >> <javascript:;>> wrote: >> > > >> >> > > >> > Agreed. >> > > >> > >> > > >> > I am committed to getting this part of the master code >> > > >> > base in Apache OODT. You’ve done amazing, Radu. >> > > >> > >> > > >> > Cheers, >> > > >> > Chris >> > > >> > >> > > >> > — >> > > >> > Chris Mattmann >> > > >> > [email protected] <javascript:;> >> > > >> > >> > > >> > >> > > >> > >> > > >> > >> > > >> > >> > > >> > >> > > >> > -----Original Message----- >> > > >> > From: Lewis John Mcgibbney <[email protected] >> > <javascript:;>> >> > > >> > Reply-To: <[email protected] <javascript:;>> >> > > >> > Date: Monday, August 24, 2015 at 10:28 PM >> > > >> > To: "[email protected] <javascript:;>" <[email protected] >> > > >> <javascript:;>>, Radu Manole >> > > >> > <[email protected] <javascript:;>> >> > > >> > Subject: Strategy for Closing off GSoC 2015 Work >> > > >> > >> > > >> > >Hi Folks, >> > > >> > >As Radu's project is coming to an end, it is wise for us to >> start >> > > >> thinking >> > > >> > >about a strategy for closing off his work. This will involve >> one or >> > > >>more >> > > >> > >of >> > > >> > >the following and potentially some other tasks. >> > > >> > > 1) Identifying final TODO's across Review Board, Jira, >> > Documentation >> > > >> and >> > > >> > >Tests. >> > > >> > > 2) Having the community test this out. Potentially by creating >> a >> > > >>branch >> > > >> > >with the work merged into it accompanied with guidelines for >> how to >> > > >>use >> > > >> > >the >> > > >> > >work and test out the functionality. >> > > >> > > 3) Thinking about merging the code into what will soon become >> OODT >> > > >> master >> > > >> > >branch. >> > > >> > >Any other ideas on top of this? >> > > >> > >@Radu, >> > > >> > >I am going through your various issues and will work with Chris >> and >> > > >>team >> > > >> > >to >> > > >> > >make sure that OODT trunk does not diverge too much from your >> work. >> > > >> > >Thank you for your work over the summer. This has been a >> > challenging >> > > >> task >> > > >> > >but one which you've done very well to schedule and address. >> > > >> > >On behalf of the OODT community, thank you. >> > > >> > >Lewis >> > > >> > > >> > > >> > >-- >> > > >> > >*Lewis* >> > > >> > >> > > >> > >> > > >> > >> > > >> >> > > > >> > > > >> > > >-- >> > > >*Lewis* >> > > >> > > >> > >> > >> > -- >> > *Lewis* >> > >> > > > > -- > *Lewis* > -- *Lewis*
