Yeah, its fairly minor. We'll put it in if we need another release candidate.
Thanks for the votes and comments Jarcec, Venkat and Abe :) Gwen On Mon, Nov 17, 2014 at 4:41 PM, Abraham Elmahrek <[email protected]> wrote: > Agreed. I'll tentatively change the fix version now. > > On Mon, Nov 17, 2014 at 3:16 PM, Venkat Ranganathan < > [email protected]> wrote: > >> Looking at the description it is a good to have this but given we have >> developer previews, agree it is OK to live with it unless there is some >> other change that warrants a respin We do need to change the fix version >> of the bug though if there are no more RCs. >> >> Venkat >> >> On Mon, Nov 17, 2014 at 2:57 PM, Abraham Elmahrek <[email protected]> >> wrote: >> >> > Just to state my perspective, it does not appear to be a blocker. >> > >> > On Mon, Nov 17, 2014 at 2:38 PM, Abraham Elmahrek <[email protected]> >> > wrote: >> > >> > > Hmm just noticed something. I've forgotten to backport SQOOP-1636 to >> > > branch-1.99.4. Do you guys think this is a blocker? This is definitely >> a >> > > nice to have for connector developers. >> > > >> > > -Abe >> > > >> > > On Mon, Nov 17, 2014 at 2:34 PM, Venkat Ranganathan < >> > > [email protected]> wrote: >> > > >> > >> +1 >> > >> >> > >> Built and ran tests on the sources >> > >> Verified checksums and signatures >> > >> No RAT violations >> > >> Check License, notices .. >> > >> >> > >> Good work folks. >> > >> >> > >> Sorry I was missing in action for the last few weeks because of other >> > >> preoccupations. >> > >> >> > >> Venkat >> > >> >> > >> On Mon, Nov 17, 2014 at 10:13 AM, Abraham Elmahrek <[email protected]> >> > >> wrote: >> > >> >> > >> > +1 (non-binding) >> > >> > >> > >> > * Verified checksums and signature files >> > >> > * Ran tests >> > >> > * Ran upgrade from 1.99.3 to 1.99.4 >> > >> > * Ran an import job and export job >> > >> > * Ran batch script for import >> > >> > >> > >> > >> > >> > On Mon, Nov 17, 2014 at 9:50 AM, Jarek Jarcec Cecho < >> > [email protected]> >> > >> > wrote: >> > >> > >> > >> > > +1 >> > >> > > >> > >> > > * Verified checksums and signature files >> > >> > > * Verified that each jar in binary tarball is in the license file >> > >> > > * Checked top level files (NOTICE, ...) >> > >> > > * Run tests >> > >> > > * Run upgrade scenario from 1.99.3 to 1.99.4 >> > >> > > >> > >> > > Jarcec >> > >> > > >> > >> > > > On Nov 16, 2014, at 3:05 PM, Gwen Shapira < >> [email protected]> >> > >> > wrote: >> > >> > > > >> > >> > > > Developers, Committers, PMC members, >> > >> > > > >> > >> > > > Thank you for testing 1.99.4 rc0 so throughly. >> > >> > > > A number of critical bugs were found and resolved. Therefore, >> > we’ve >> > >> > > > packaged up a new release candidate. >> > >> > > > >> > >> > > > The second release candidate of the fourth release of Apache >> Sqoop >> > >> 2, >> > >> > > > version 1.99.4 is ready. >> > >> > > > >> > >> > > > Please vote by Monday, November 24. >> > >> > > > >> > >> > > > Change log: >> > >> > > > >> > >> https://github.com/apache/sqoop/blob/release-1.99.4-rc1/CHANGELOG.txt >> > >> > > > >> > >> > > > The tarball (*.tar.gz), signature (*.asc), checksum (*.md5): >> > >> > > > http://people.apache.org/~jarcec/sqoop-1.99.4-rc1/ >> > >> > > > >> > >> > > > The tag to be voted on: >> > >> > > > >> > >> > > >> > >> > >> > >> >> > >> https://git-wip-us.apache.org/repos/asf?p=sqoop.git;a=tag;h=refs/tags/release-1.99.4-rc1 >> > >> > > > >> > >> > > > The KEYS file: >> > >> > > > https://dist.apache.org/repos/dist/release/sqoop/KEYS >> > >> > > > >> > >> > > > (Note that the tarball is in Jarcec's home directory, but its >> > signed >> > >> > > > with my keys) >> > >> > > > >> > >> > > > Keep calm and vote, >> > >> > > > >> > >> > > > Gwen >> > >> > > >> > >> > > >> > >> > >> > >> >> > >> -- >> > >> 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. >> > >> >> > > >> > > >> > >> >> -- >> 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. >>
