Pavel, How will the contribution process be affected if the community switches to Upsource? Will Upsource introduce additional steps for those who want to ask someone to review a branch or the tool simply intercepts all the pull-requests automatically?
Cos, Raul, Others, How this intention is aligned with Apache at all? In you experience, are there any examples of Apache projects that used some 3rd party tool for review process? — Denis > On Nov 14, 2016, at 4:08 AM, Pavel Tupitsyn <[email protected]> wrote: > > Igniters, > > We have set up Upsource code review tool at > http://reviews.ignite.apache.org/ > > I propose to evaluate it and see if it works for us. > > > * Why? > Current JIRA-based process is not very efficient. Anyone who have used a > review tool will probably agree: > > - No need to switch branches locally and interrupt your current work. You > can see the code in one click. > - All current reviews are easily accessible > - Multiple reviewers > - Much better discussions: comments are right in the code; each point can > be discussed and accepted separately > - Integrates with IDEA - open the diff in IDEA in one click, or see the > reviews there without opening the browser at all > > > * Why Upsource? > I've evaluated a bunch of tools (CodeCollaborator, ReviewBoard, > Phabricator, Crucible), > and Upsource looks like the best fit for us: > - PR-based code reviews. This is a major advantage: review for a PR can be > created in one click, and it updates automatically when you push more > commits (fix review issues) > - Good Java support and IDEA integration > - Good performance (our code base is big, and tools like Crucible really > struggle with it) > > > Thoughts and suggestions are welcome. > > Thanks, > > Pavel
