Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (athena.apache.org: domain of bmathus@gmail.com designates
 74.125.83.52 as permitted sender)
MIME-Version: 1.0
Sender: bmathus@gmail.com
In-Reply-To: <10749063.jC47tyPmt6@herve-desktop>
References: 
 <CA+nPnMyvQ6jryMhPSGb-BMkFCF9CwRu_1AiTE92ZLXwp8dPsKQ@mail.gmail.com>
	<CADN69yn4dg50i8yUtgSBeaEim4KxzdxdEGffcKtpwVSeihw2pA@mail.gmail.com>
	<10749063.jC47tyPmt6@herve-desktop>
Date: Fri, 2 Aug 2013 20:27:47 +0200
Message-ID: 
 <CANWgJS6qXuV46jHZ2mbn3rriZYN0mZfV-90vt4dc9G5iTZ-MgQ@mail.gmail.com>
Subject: Re: [DISCUSS] On the Maven PMC roles... (was [DISCUSS] Should the
 Maven PMC be an example of how we want the Maven Community to behave...)
From: Baptiste MATHUS <ml@batmat.net>
To: Maven Users List <users@maven.apache.org>
Content-Type: multipart/alternative; boundary=047d7b6041ca90cd7f04e2fb1d9f

--047d7b6041ca90cd7f04e2fb1d9f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Le 2 ao=C3=BBt 2013 17:48, "Herv=C3=A9 BOUTEMY" <herve.boutemy@free.fr> a =
=C3=A9crit :
>
> Le vendredi 2 ao=C3=BBt 2013 10:08:42 Curtis Rueden a =C3=A9crit :
> > True, and it is good to warn about this. However, ultimately I think
Git is
> > a better choice (than SVN) because it often makes code review much
easier.
> I didn't use gerrit nor have seen anybody using it. But I hear about it
more
> and more often as an argument why it makes git better than svn (even if I
read
> that gerrit is a fork of rietveld, which is the same for subversion: but
> nobody even talks about it, don't know why).
> Is this pure theory? a dream? a reality for a minority of experts, talkin=
g
> about it loudly but no mere mortal can use it?
> (intentional provocational tone to motivate people who know to show me th=
e
> direction to the light :) )

Just my 2 cents : been using gerrit professionally on a daily basis for 8
months now. So there's actually real people using it, I can testify ;).

We're a team of ~10 guys.

(For French savvy people I've given a short talk about it at the Toulouse
jug. The session was recorded ans is hosted on parleys).

>
> > If a new feature is properly developed on a topic branch with commits
> > squashed, rewritten and organized as needed, the history can be laid
out in
> > a very easy-to-understand manner: new features and bugfixes done in
> > properly isolated commits, unit tests added immediately thereafter, etc=
.
> yes, with git, you can: with git, so much things can be done.
> But once again, I didn't see anybody do it, because it's a lot of work.

You're right. I try to do it as often as I can. But perfection takes a bit
too long to commit/rework and sometimes it's ridiculous ;).

> And it requires to be a git black belt.

It helps to practice, sure. Btw, Gerrit makes it worse. It almost forces
you to use advances features to make it really useful.
That's why I'd say putting a whole team both beginning with git and gerrit
would be a mistake.

> For the moment, just making a rebase before merging a branch seems hard
for us
> mere mortals.
>
> > If
> > a commit is too large or conflates many different changes, Git provides
the
> > tools to split up that work for rereview.
> >
> > Again, thanks for writing this.
> +1
> I like it too
>
> Regards,
>
> Herv=C3=A9
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>

--047d7b6041ca90cd7f04e2fb1d9f--