Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of ryanobjc@gmail.com designates
 209.85.212.169 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=pU5qC/qQTnJryHDTDRksKaCp+XIC66ylPKmJN96KjjP1Bam0s/cW7iEyj2yhdSzXFj
         7HR31Hm+tgBlr85Rh/yg/PyDPWMpm9jSIiFl+toDQwomogK4PHGyoMxLeFAw1AZMZ1fo
         JSsTuY+i1iat2qEyMdZ0spS8yY2udwEy19Wrw=
MIME-Version: 1.0
Date: Fri, 21 May 2010 15:56:42 -0700
Message-ID: <AANLkTin5qgReMGpWlXVwWs67hDrEQzyYEls7KY6u24AO@mail.gmail.com>
Subject: Review board for all/most JIRAs patches
From: Ryan Rawson <ryanobjc@gmail.com>
To: dev@hbase.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

To make the life of reviewers easier, as well as improving review turn
around time, we are requesting all contributors (committers and
otherwise) to submit patches to http://review.hbase.org/ in addition
to attaching them to JIRAs.  Review board has a nice API which allows
people to review diffs without downloading a patch and applying it,
and it is source code aware and will allow a reviewer to expand the
context.  It works with both SVN diffs and GIT diffs for those who use
one or the other (or both) to develop their diffs.  (I have to
recommend git - it makes rebasing and keeping a patch current much
easier, especially with the latest trunk turmoil).

If the patch is more than 2 files, please make everyone's life easier
by review boarding it!

I'm checking to see if it is possible to have reviewboard's email
cause JIRA comments.  Hopefully it will and then we will have a full
record and a better UI.

-ryan