Mailing-List: contact dev-help@ignite.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of dsetrakyan@gridgain.com
 designates 209.85.192.171 as permitted sender)
From: Dmitriy Setrakyan <dsetrakyan@gridgain.com>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: jira status for reviews
Message-Id: <FC57E2BB-588D-46EC-A507-AF6488401EDD@gridgain.com>
Date: Sun, 18 Jan 2015 11:17:21 -0800
References: 
 <CA+0=VoX_XcBL=tCFrOK=p+SnazzmradPFAGk16YDmT=ASFQMNA@mail.gmail.com>
 <20150118191419.GE4732@boudnik.org>
In-Reply-To: <20150118191419.GE4732@boudnik.org>
To: "dev@ignite.incubator.apache.org" <dev@ignite.incubator.apache.org>

How do I find all the available workflows?

Dmitriy


> On Jan 18, 2015, at 11:14 AM, Konstantin Boudnik <cos@apache.org> wrote:
>=20
> In Bigtop, we are using "Patch Available" state for that and it works pret=
ty
> well, as far as I can tell. Here's the flow diagram for your attention:
>=20
>  https://issues.apache.org/jira/plugins/servlet/project-config/BIGTOP/work=
flows
>=20
> The case you propose below would be addressed by moving between "In Progre=
ss"
> and "Patch Available" until the fix is ready to be merged/committed to the=

> mainline.
>=20
> If this is something that might work - and this is pretty standard
> flow, so no one will need to learn the ropes - you can ask INFRA to assign=

> this flow to IGNITE project.
>=20
> Cos
>=20
>> On Sun, Jan 18, 2015 at 10:23AM, Dmitriy Setrakyan wrote:
>> While we are trying to find a way to customize Jira workflow, in the mean=

>> time we need to have a Jira status for issues that need to be peer-review=
ed
>> by a committer.
>>=20
>> I propose using Resolve workflow for it. Whenever issue is ready for
>> review, Resolve it and assign to a committer who, in your opinion is the
>> best person to do a review. If  the issue passes the review, then it can b=
e
>> merged and closed. Otherwise, it should be reopened and assigned back to
>> the developer.
>>=20
>> Any objections?
>>=20
>> D.