Hi Ajay, [1] Venkat signed the key. Will verify the signing process again. [2] FALCON-1858 : I was thinking in the lines that this should be listed under behavioral change since users can continue to use Berkeley DB storage if they wish to. But I now agree with your argument that change in default settings should be mentioned under incompatible changes. [3] Will update NOTICE and verify what depends on JTS.
Thanks Balu Vellanki On 7/26/16, 4:16 AM, "Ajay Yadava" <[email protected]> wrote: >Balu, Venkat, > >I haven't finished my checks but it seems I have hit a blocker. I verified >following: > > - Verified the signature > >Was able to receive the key and verify the signature but *[1]* > > - Verified md5 and sha512 > - Checked release Notes *[2]* > - License and Notice > >*NOTICE* >Copyright notice is 2015 and should be extended to 2016. >*Licensing* >There is a dependency on JTS which has LGPL license *[3]* > >AFAIK LGPL is incompatible and shouldn't be bundled. > > > >[1] Balu's key is not signed by anyone else so not in my WOT. > >[2] FALCON-1858 is a backward incompatible change because it has changed >the default settings and will be surprising for existing users. It should >be mentioned under incompatible changes in release notes. > > >*[FALCON-1858] - Support HBase as a storage backend for Falcon Titan >graphDB. Users will be able to choose between HBase (default) and the >current Berkeley DB storage* > >[3] http://www.vividsolutions.com/jts/JTSHome.htm
