This submodule will still be under the review-then-commit (RTC) regime, correct?
On 4 February 2015 at 11:13, Yi Pan <nickpa...@gmail.com> wrote: > Just did the update w/ SAMZA-482. > > On Wed, Feb 4, 2015 at 10:31 AM, Chris Riccomini <criccom...@apache.org> > wrote: > >> I think so. There was some RB downtime, but it just got fixed. Yi, Navina, >> Milinda, can you make sure your JIRAs have up to date RBs? >> >> On Wed, Feb 4, 2015 at 10:24 AM, sriram <sriram....@gmail.com> wrote: >> >> > Can we have updated RBs for all the three sub tasks before we commit? >> This >> > would help us to review even after we commit. >> > >> > On Wed, Feb 4, 2015 at 10:15 AM, Chris Riccomini <criccom...@apache.org> >> > wrote: >> > >> > > Hey all, >> > > >> > > Yi, Navina, and Milinda have been working on SAMZA-390 sub-tickets >> > related >> > > to SQL operators. We're getting to the point where the amount of work >> > > floating around is quite large, and some tickets build off of others. >> > > >> > > I'm proposing that we commit this work into a samza-sql submodule on >> > > master, and treat this module as experimental. I want to avoid >> branches, >> > > and I also want to avoid revision control over JIRA. This means that >> > there >> > > will probably be a fair amount of commits/JIRAs on this module as we >> > > iterate, but I think that's OK. >> > > >> > > Does this sound good to everyone? >> > > >> > > Cheers, >> > > Chris >> > > >> > >>
