Can someone please clarify what is going on here. Am I correct that Tranquility is not an Apache project? Who is allowed to vote for this release - Druid PPMC members?
What is being voted upon? A particular set of artifacts to be released, the latest commit in github, or something else? (If it’s not an Apache release, I guess I shouldn’t complain that the vote doesn’t follow Apache protocol.) Julian > On Oct 15, 2018, at 7:51 PM, David Lim <[email protected]> wrote: > > +1 > > On Mon, Oct 15, 2018 at 6:08 PM Fangjin Yang <[email protected]> wrote: > >> +1 >> >> On Mon, Oct 15, 2018 at 4:40 PM Jihoon Son <[email protected]> wrote: >> >>> +1 >>> >>> Thanks Jon! >>> >>> Jihoon >>> >>> On Tue, Oct 16, 2018 at 5:22 AM Jonathan Wei <[email protected]> wrote: >>> >>>> Hi all, >>>> >>>> I'd like to open a vote for a new Tranquility release, 0.8.3. The new >>>> release would have the following improvements and bug fixes: >>>> >>>> Improvements: >>>> * Update Curator and Scala. (#213) >>>> * support rollup function in druid 0.9.2 (#210) >>>> * Allow customization of zookeeper path through properties. (#215) >>>> * Update MMX libraries and replace scala_tools.time (#220) >>>> * Exclude deps with *GPL licenses. (#223) >>>> * expose sslContext and prefer tlsPort if present (#257) >>>> * Support Basic HTTP auth with druid, TLS support for server (#277) >>>> >>>> Bug fixes: >>>> * remove data type and input row parser type binding (#193) >>>> * Change default host/port for DruidNode and FlinkBeam (#266) >>>> * Thread-safe samza BeamProducer (#228) >>>> >>>> Notably, this release would allow Tranquility to work with TLS-secured >>>> Druid clusters and support Basic HTTP user/pass authentication. >>>> >>>> Thanks, >>>> Jon >>>> >>> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
