Thank you Abe and Jarcec for stepping up for the next release of Sqoop. Regards, Arvind Prabhakar
On Wed, Jul 2, 2014 at 8:43 AM, Jarek Jarcec Cecho <[email protected]> wrote: > It seems that we have an agreement on the doing the release and a > community volunteer! Thank you Abe for taking the responsibility of Release > Manager! > > I'll start working with Abe on the release to explain what and how needs > to be done even though that we're still waiting on some of the patches to > come in. > > Jarcec > > On Wed, Jul 02, 2014 at 08:03:37AM -0700, Gwen Shapira wrote: > > +1 for 1.4.5 release > > +1 for Abe as release manager > > and +1 for Venkat getting his patches in (especially if this includes the > > Oracle Wallet patch) > > > > Gwen > > > > > > On Wed, Jul 2, 2014 at 7:01 AM, Kathleen Ting <[email protected]> > wrote: > > > > > +1 on doing a 1.4.5 release > > > +1 on Abe as release manager > > > > > > On Wed, Jul 2, 2014 at 12:10 AM, Venkat Ranganathan > > > <[email protected]> wrote: > > > > +1. I would like to get couple of patches in. Will rebase and get > > > > the patch for review in the next few days. > > > > > > > > Thanks > > > > > > > > Venkat > > > > > > > > On Tue, Jul 1, 2014 at 8:20 PM, Jarek Jarcec Cecho < > [email protected]> > > > wrote: > > > >> Hi Martin, > > > >> I'm excited to see you interest in helping out with OraOop > integration. > > > The documentation work is covered by > > > https://issues.apache.org/jira/browse/SQOOP-1344 and we should > definitely > > > incorporate that before cutting a release. I would suggest you to > follow up > > > on that JIRA asking what you can help with :-) I'm sure that there > will be > > > ton of opportunities! > > > >> > > > >> Jarcec > > > >> > > > >> On Wed, Jul 02, 2014 at 01:38:32AM +0000, Martin, Nick wrote: > > > >>> Housekeeping-wise...hoping the new release will have ample > > > documentation around the OraOop piece. That in the works? > > > >>> > > > >>> I'm happy to volunteer for any low hanging fruit around > documentation > > > cleanup and/or kicking the tires in a heavy Oracle enviro. Just let me > know > > > if there's any of that kind of thing I can tackle to free up folks for > > > heavy lifting. > > > >>> > > > >>> Excited! We've been patiently waiting for this and thanks to the > > > community for all the hard work. Great stuff... > > > >>> > > > >>> Sent from my iPhone > > > >>> > > > >>> On Jul 1, 2014, at 9:19 PM, "Abraham Elmahrek" <[email protected]> > > > wrote: > > > >>> > > > >>> > I'm +1 to this. I'd also like to volunteer for doing the release. > > > >>> > > > > >>> > > > > >>> > On Tue, Jul 1, 2014 at 5:50 PM, Jarek Jarcec Cecho < > > > [email protected]> > > > >>> > wrote: > > > >>> > > > > >>> >> Some time back we've decided to wait with 1.4.5 release until we > > > will get > > > >>> >> in OraOop connector. The connector is in now so I'm wondering > what > > > would > > > >>> >> people think about doing another release? > > > >>> >> > > > >>> >> The number of changes that went into trunk after 1.4.4 is quite > > > impressive > > > >>> >> - 51 [1] including but not limited to a big features such as the > > > OraOop > > > >>> >> connector or Accumulo support. > > > >>> >> > > > >>> >> If there will be agreement on doing the release, then I would > > > propose to > > > >>> >> follow the approach we were doing last couple of releases. One > of > > > the > > > >>> >> committers/PMC member will volunteer as a Release mentor and > will > > > mentor > > > >>> >> one community volunteer. I'm more then happy to sign up for the > > > mentorship. > > > >>> >> > > > >>> >> Jarcec > > > >>> >> > > > >>> >> Links: > > > >>> >> 1: > > > >>> >> > > > > https://issues.apache.org/jira/browse/SQOOP-1341?jql=project%20%3D%20SQOOP%20and%20fixVersion%20%3D%20%221.4.5%22%20and%20status%20%3D%20resolved > > > >>> >> > > > > > > > > -- > > > > CONFIDENTIALITY NOTICE > > > > NOTICE: This message is intended for the use of the individual or > entity > > > to > > > > which it is addressed and may contain information that is > confidential, > > > > privileged and exempt from disclosure under applicable law. If the > reader > > > > of this message is not the intended recipient, you are hereby > notified > > > that > > > > any printing, copying, dissemination, distribution, disclosure or > > > > forwarding of this communication is strictly prohibited. If you have > > > > received this communication in error, please contact the sender > > > immediately > > > > and delete it from your system. Thank You. > > > >
