On Friday, April 27, 2012 10:49:22 am Nasser Grainawi wrote:
> On Apr 27, 2012, at 10:22 AM, Magnus Bäck wrote:
> > On Friday, April 27, 2012 at 12:08 EDT,
> >
> > Martin Fick <
mf...@codeaurora.org> wrote:
> >> For that matter, I think I recall someone requesting a
> >> way to review branch creation also. Perhaps what we
> >> need is some sort of pseudo changes. We could have a
> >> CREATE_PROJECT pseudo change and a CREATE_BRANCH
> >> pseudo change, perhaps a DELETE_BRANCH also?
> >
> > Ah, yes. Even for organizations that are liberal with
> > branch creations, non fast-forward ref updates might
> > be limited to a very small number of people. Right now
> > they're getting the requests via email or some outside
> > ticket system.
> >
> > (I'm getting a tingling sense of featuritis here. But
> > it would be cool stuff, and certainly useful for
> > several companies using Gerrit.)
>
> Yeah, it does start to encroach on the "Gerrit as an
> issue tracker" idea that Shawn originally pushed away
> from.
Agreed, but the key advantage is that the review can be
encoded in Gerrit in a way which is actionable. With any
other ticketing system there will always need to be some
translation layer to then get it implemented in Gerrit.
This means everyone is doing it differently, and it is
likely to break in the future if Gerrit changes. And quite
simply that is more work: how do you know to really close a
ticket, how can you verify that it was implemented as
requested? With this in Gerrit, you would get a lot for
free that simply is not possible in a reliable way with any
other system,
-Martin
--
Employee of Qualcomm Innovation Center, Inc. which is a