Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 29 Aug 2016 00:41:15 +0100
From: Aleksey Yeschenko <aleksey@apache.org>
To: dev@cassandra.apache.org
Message-ID: <etPan.57c3769b.2122dc57.335@apache.org>
In-Reply-To: <1472424559.3422783.708617905.3C18BE03@webmail.messagingengine.com>
References: <1472424559.3422783.708617905.3C18BE03@webmail.messagingengine.com>
Subject: Re: in-tree 'Cassandra Development' docs
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="57c3769b_2e712266_335"
archived-at: Sun, 28 Aug 2016 23:41:22 -0000

--57c3769b_2e712266_335
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Can=E2=80=99t really forcefully assign work, including review work, to vo=
lunteers.

So I=E2=80=99m not sure what we can do here, other than perhaps create so=
me sort of dashboard
to show tickets with unassigned reviewers, and tickets with overdue revie=
ws.

Both can be easily done as JIRA filters, however.

As an individual volunteer committer, you just pick JIRAs you want to wor=
k on/review, if they aren=E2=80=99t taken.
If they are taken, you talk to the current assignee and ask them to take =
over. Usually if they aren=E2=80=99t far in,
they=E2=80=99ll happily yield, in my experience.

--=C2=A0
AY

On 28 August 2016 at 23:49:23, mck (mck=40apache.org) wrote:


http://cassandra.apache.org/doc/latest/development/index.html =20


This is fantastic. Thanks heaps and heaps for doing this. =20
Stefan i believe you get some of the credit for this=21 =20


The top level 'Community' link now seems a bit superfluous. I guess =20
there are plans for this=3F =20

There's also no docs on how which tickets get reviewed. =20
As far as i know DS has an internal system for this, which is fair =20
enough. But it would be nice to know more (and see =20
formalised/documented) about how the tickets to review are pulled, how =20
they'll split into different areas of code to make it easier for =20
committers to review, and how tickets don't get forgotten along the way. =
=20
I've had a number of tickets where the reviewer just 'disappeared' and =20
many months went by. This is a potential source of frustration for =20
contributors. =20

Mick. =20

--57c3769b_2e712266_335--