attu Parambil" <rkavu...@redhat.com>,
gluster-devel@gluster.org
Sent: Tuesday, July 7, 2015 2:48:22 PM
Subject: Re: [Gluster-devel] Automated bug workflow
On 07/07/2015 02:42 PM, Rafi Kavungal Chundattu Parambil wrote:
>
> Since we have some common interest in proposed design, IMHO l
Message -
>> From: "Pranith Kumar Karampuri" <pkara...@redhat.com>
>> To: "Rafi Kavungal Chundattu Parambil" <rkavu...@redhat.com>,
>> gluster-devel@gluster.org
>> Sent: Tuesday, July 7, 2015 2:48:22 PM
>> Subject: Re: [Gluster-devel] A
...@redhat.com
To: Niels de Vos nde...@redhat.com, gluster-devel@gluster.org
Sent: Friday, May 29, 2015 11:23:34 PM
Subject: Re: [Gluster-devel] Automated bug workflow
On 05/29/2015 12:51 PM, Niels de Vos wrote:
Hi all,
today we had a discussion about how to get the status of reported bugs
more
29, 2015 11:23:34 PM
Subject: Re: [Gluster-devel] Automated bug workflow
On 05/29/2015 12:51 PM, Niels de Vos wrote:
Hi all,
today we had a discussion about how to get the status of reported bugs
more correct and up to date. It is something that has come up several
times already, but now we have
On Fri, May 29, 2015 at 01:53:34PM -0400, Shyam wrote:
On 05/29/2015 12:51 PM, Niels de Vos wrote:
Hi all,
today we had a discussion about how to get the status of reported bugs
more correct and up to date. It is something that has come up several
times already, but now we have a BIG
Hi all,
today we had a discussion about how to get the status of reported bugs
more correct and up to date. It is something that has come up several
times already, but now we have a BIG solution as Pranith calls it.
The goal is rather simple, but is requires some thinking about rules and
When similar automation was discussed, somebody had raised the concern when
more than one patch is associated with a BZ. Either we keep 1:1 between BZ and
patch. Otherwise the workflow needs to be improvised to inform gerrit when the
last patch is submitted for a BZ so that the state can be
On 05/29/2015 12:51 PM, Niels de Vos wrote:
Hi all,
today we had a discussion about how to get the status of reported bugs
more correct and up to date. It is something that has come up several
times already, but now we have a BIG solution as Pranith calls it.
The goal is rather simple, but is
On 05/29/2015 10:41 PM, Nagaprasad Sathyanarayana wrote:
When similar automation was discussed, somebody had raised the concern when
more than one patch is associated with a BZ. Either we keep 1:1 between BZ and
patch. Otherwise the workflow needs to be improvised to inform gerrit when the
On 05/29/2015 11:23 PM, Shyam wrote:
On 05/29/2015 12:51 PM, Niels de Vos wrote:
Hi all,
today we had a discussion about how to get the status of reported bugs
more correct and up to date. It is something that has come up several
times already, but now we have a BIG solution as Pranith calls
10 matches
Mail list logo
