Concluding the vote with six binding +1 votes (out of seven +1 votes) and no 0 or no -1 votes.
Thanks Amareshwari On Fri, Sep 13, 2019 at 1:08 PM Raghavendra Singh <[email protected]> wrote: > +1 > > On Fri, Sep 13, 2019 at 11:44 AM Srikanth Sundarrajan <[email protected] > > > wrote: > > > +1 (binding) > > > > Regards > > Srikanth Sundarrajan > > ________________________________ > > From: rajitha r <[email protected]> > > Sent: Friday, September 13, 2019 10:22 AM > > To: dev <[email protected]> > > Subject: Re: [VOTE] Break up lens code into two sub projects > > > > +1 > > > > On Fri, Sep 13, 2019 at 9:39 AM Raju Bairishetti <[email protected]> > > wrote: > > > > > +1 > > > > > > On Thu, 12 Sep 2019, 11:53 Rajat Khandelwal, <[email protected]> > > > wrote: > > > > > > > +1 > > > > > > > > > > > > Rajat Khandelwal > > > > > > > > On Wed, 28 Aug, 2019, 17:18 Puneet Gupta, <[email protected]> > > > wrote: > > > > > > > > > +1 from me. > > > > > > > > > > On Wed, 28 Aug, 2019, 4:42 PM Amareshwari Sriramdasu, < > > > > > [email protected]> wrote: > > > > > > > > > > > +1 from my side. > > > > > > > > > > > > On Wed, Aug 28, 2019 at 4:41 PM Amareshwari Sriramdasu < > > > > > > [email protected]> wrote: > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > After the discussion on Lens roadmap thread, calling this vote > to > > > get > > > > > > > consensus from developers of Lens for the proposal. > > > > > > > > > > > > > > Lens codebase can be broken down into two sub projects : one > for > > > > > > metastore > > > > > > > and other for query. Query service can have dependency on > > metastore > > > > > > > service. This shall help these subprojects evolve separately. > > > > > > > > > > > > > > To achieve the same we shall do 2.8 release from current master > > > with > > > > > all > > > > > > > changes for current stack. Move master to 3.0 with refactored > > code > > > of > > > > > > > subprojects, which can be build separately. > > > > > > > > > > > > > > Lens developers, do cast your vote for the above > > > > > > > > > > > > > > [+1] if you approve > > > > > > > [0] if no opinion > > > > > > > [-] if you are not approving, with reasons. > > > > > > > > > > > > > > Do express your comments as well. > > > > > > > > > > > > > > Thanks > > > > > > > Amareshwari > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > Regards, > > > > Rajitha.R > > > > -- > _____________________________________________________________ > The > information contained in this communication is intended solely for the use > of the individual or entity to whom it is addressed and others authorized > to receive it. It may contain confidential or legally privileged > information. If you are not the intended recipient you are hereby notified > that any disclosure, copying, distribution or taking any action in > reliance > on the contents of this information is strictly prohibited and may be > unlawful. If you have received this communication in error, please notify > us immediately by responding to this email and then delete it from your > system. The firm is neither liable for the proper and complete > transmission > of the information contained in this communication nor for any delay in > its > receipt. >
