You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by Hari Shreedharan <hs...@cloudera.com> on 2012/08/26 19:48:10 UTC
[DISCUSS] Experimenting with gerrit
Hi,
Since it has been some time since we moved to git, I think now is a good time to experiment with review tools that integrate well with git. I'd like to propose that we experiment with gerrit. Gerrit has the ability to commit the changes directly to the repo once changes are +1-ed. This way we will be able to enforce the RTC policy in a much easier way, and also we can avoid accidental commits from the local repo getting pushed. I am not sure how the hosting would work, but gerrit as it is is ASL2.0 licensed (http://code.google.com/p/gerrit/). I have never used it before, but have heard reasonably good reviews of the tool, especially its direct commit functionality.Please post your thoughts on this thread.
Thanks,
Hari
--
Hari Shreedharan
Re: [DISCUSS] Experimenting with gerrit
Posted by Mike Percy <mp...@apache.org>.
Same here, I'd be happy to try it out.
Regards,
Mike
On Mon, Aug 27, 2012 at 8:11 AM, Brock Noland <br...@cloudera.com> wrote:
> I would not mind trying it.
>
> On Mon, Aug 27, 2012 at 12:29 AM, Jarek Jarcec Cecho <jarcec@apache.org
> >wrote:
>
> > I also do not have any prior experience with it, but I don't mind trying
> > it out.
> >
> > Jarcec
> >
> > On Sun, Aug 26, 2012 at 10:48:10AM -0700, Hari Shreedharan wrote:
> > > Hi,
> > >
> > > Since it has been some time since we moved to git, I think now is a
> good
> > time to experiment with review tools that integrate well with git. I'd
> like
> > to propose that we experiment with gerrit. Gerrit has the ability to
> commit
> > the changes directly to the repo once changes are +1-ed. This way we will
> > be able to enforce the RTC policy in a much easier way, and also we can
> > avoid accidental commits from the local repo getting pushed. I am not
> sure
> > how the hosting would work, but gerrit as it is is ASL2.0 licensed (
> > http://code.google.com/p/gerrit/). I have never used it before, but have
> > heard reasonably good reviews of the tool, especially its direct commit
> > functionality.Please post your thoughts on this thread.
> > >
> > >
> > > Thanks,
> > > Hari
> > >
> > > --
> > > Hari Shreedharan
> > >
> > >
> >
>
>
>
> --
> Apache MRUnit - Unit testing MapReduce -
> http://incubator.apache.org/mrunit/
>
Re: [DISCUSS] Experimenting with gerrit
Posted by Brock Noland <br...@cloudera.com>.
I would not mind trying it.
On Mon, Aug 27, 2012 at 12:29 AM, Jarek Jarcec Cecho <ja...@apache.org>wrote:
> I also do not have any prior experience with it, but I don't mind trying
> it out.
>
> Jarcec
>
> On Sun, Aug 26, 2012 at 10:48:10AM -0700, Hari Shreedharan wrote:
> > Hi,
> >
> > Since it has been some time since we moved to git, I think now is a good
> time to experiment with review tools that integrate well with git. I'd like
> to propose that we experiment with gerrit. Gerrit has the ability to commit
> the changes directly to the repo once changes are +1-ed. This way we will
> be able to enforce the RTC policy in a much easier way, and also we can
> avoid accidental commits from the local repo getting pushed. I am not sure
> how the hosting would work, but gerrit as it is is ASL2.0 licensed (
> http://code.google.com/p/gerrit/). I have never used it before, but have
> heard reasonably good reviews of the tool, especially its direct commit
> functionality.Please post your thoughts on this thread.
> >
> >
> > Thanks,
> > Hari
> >
> > --
> > Hari Shreedharan
> >
> >
>
--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
Re: [DISCUSS] Experimenting with gerrit
Posted by Jarek Jarcec Cecho <ja...@apache.org>.
I also do not have any prior experience with it, but I don't mind trying it out.
Jarcec
On Sun, Aug 26, 2012 at 10:48:10AM -0700, Hari Shreedharan wrote:
> Hi,
>
> Since it has been some time since we moved to git, I think now is a good time to experiment with review tools that integrate well with git. I'd like to propose that we experiment with gerrit. Gerrit has the ability to commit the changes directly to the repo once changes are +1-ed. This way we will be able to enforce the RTC policy in a much easier way, and also we can avoid accidental commits from the local repo getting pushed. I am not sure how the hosting would work, but gerrit as it is is ASL2.0 licensed (http://code.google.com/p/gerrit/). I have never used it before, but have heard reasonably good reviews of the tool, especially its direct commit functionality.Please post your thoughts on this thread.
>
>
> Thanks,
> Hari
>
> --
> Hari Shreedharan
>
>