+1 On Wed, Nov 1, 2017 at 3:51 AM, Arina Yelchiyeva <arina.yelchiy...@gmail.com > wrote:
> +1 but as we have communicated on Hangouts committer should be responsible > for: > > 1. making sure that there is only one commit (otherwise ask developer to > squash the commits, unless several commits are required) and commit message > is according to the Drill standards. > 2. all unit tests pass. > 3. all functional and advanced tests pass ( > https://github.com/mapr/drill-test-framework). > > Kind regards > Arina > > On Tue, Oct 31, 2017 at 11:53 PM, Charles Givre <cgi...@gmail.com> wrote: > > > I’d vote +1 for moving to gitbox. > > — C > > > > > On Oct 31, 2017, at 13:54, Parth Chandra <par...@apache.org> wrote: > > > > > > Bumping this thread up. > > > > > > Vlad brought this up in the hangout today and it sounds like we would > > like > > > to move to Gitbox. Thanks Vlad for the patient explanations! > > > > > > Committers, let's use this thread to vote on the the suggestion. > > > > > > I'm +1 on moving to gitbox. > > > > > > Also, I can work with Vlad and Paul on updating the merge process > > document. > > > > > > > > > > > > On Wed, Aug 30, 2017 at 1:34 PM, Vlad Rozov <vro...@apache.org> wrote: > > > > > >> Hi, > > >> > > >> As I am new to Drill, I don't know if migration from "Git WiP" ( > > >> https://git-wip-us.apache.org) to "Github Dual Master" ( > > >> https://gitbox.apache.org) was already discussed by the community, > but > > >> from my Apache Apex experience I would recommend to consider migrating > > >> Drill ASF repos to the gitbox. Such move will give committers write > > access > > >> to the Drill repository on Github with all the perks that Github > > provides. > > >> > > >> Thank you, > > >> > > >> Vlad > > >> > > > > >
