[RESULT] [VOTE] Separate Avatica into its own repository

This vote passes with 4 +1's (1 non-binding). Thanks for those who took the time to provide their opinion! I'll try to proceed with this today. Josh Elser wrote: Hi all, Hopefully you've all caught the discussion on this subject by now (CALCITE-1717, and this thread[1]). A few of us are

Re: [VOTE] Separate Avatica into its own repository

+1 (non-binding) On Mon, Mar 27, 2017 at 11:43 AM Laurent Goujon wrote: > +1 > > On Sun, Mar 26, 2017 at 1:25 PM, James Taylor > wrote: > > > +1 > > > > On Sun, Mar 26, 2017 at 1:15 PM Julian Hyde wrote: > > > > > +1 > > > > > >

Re: [VOTE] Separate Avatica into its own repository

+1 On Sun, Mar 26, 2017 at 1:25 PM, James Taylor wrote: > +1 > > On Sun, Mar 26, 2017 at 1:15 PM Julian Hyde wrote: > > > +1 > > > > Thanks for running this vote, Josh. > > > > > On Mar 26, 2017, at 10:05 AM, Josh Elser wrote: > > >

Re: [VOTE] Separate Avatica into its own repository

+1 On Sun, Mar 26, 2017 at 1:15 PM Julian Hyde wrote: > +1 > > Thanks for running this vote, Josh. > > > On Mar 26, 2017, at 10:05 AM, Josh Elser wrote: > > > > Hi all, > > > > Hopefully you've all caught the discussion on this subject by now >

Re: [VOTE] Separate Avatica into its own repository

+1 Thanks for running this vote, Josh. > On Mar 26, 2017, at 10:05 AM, Josh Elser wrote: > > Hi all, > > Hopefully you've all caught the discussion on this subject by now > (CALCITE-1717, and this thread[1]). A few of us are leaning towards > physically separating the

[VOTE] Separate Avatica into its own repository

Hi all, Hopefully you've all caught the discussion on this subject by now (CALCITE-1717, and this thread[1]). A few of us are leaning towards physically separating the Avatica and Calcite codebases. We think that this will ultimately help each project grow at their own rate and give us more