I don't have comment permissions on the doc, but it looks like you omitted
a way to go from Reviewable -> In Progress, which we often do when the
reviewee has more work to do before being ready for additional reviews, for
example.

I'm not sure what 'Closed' is supposed to represent, what does it mean to
go from Resolved to Closed?

On Tue, Jun 9, 2015 at 3:41 PM, Marco Massenzio <[email protected]> wrote:

> Hi Vinod,
>
> thanks for super-quick reply.
> We've already been through this in our internal (Mesosphere) Jira (on a
> completely different topic) so I know that this can be done, if we use our
> own "custom Mesos" workflow (here:
> https://issues.apache.org/jira/plugins/servlet/project-config/MESOS/workflows)
> which I think we already do.
>
> I would probably need to be given adequate permissions to modify it
> (avoiding to mess up in the process the entirety of ASF :)
> Once we agree that the proposed one works for folks here, I'll work with
> Jake and Infra folks, and figure out how to implement.
>
> Thanks!
>
> *Marco Massenzio*
> *Distributed Systems Engineer*
>
> On Tue, Jun 9, 2015 at 3:15 PM, Vinod Kone <[email protected]> wrote:
>
>> +jake
>>
>> Marco, this sounds good to me. Have you looked into see if JIRA allows us
>> to constrain ourselves to this workflow? If yes, the next step would be to
>> work with ASF infra to see if they are ok with us adopting a new workflow.
>> IIRC, there are some JIRA settings that are global to all ASF projects and
>> hence can't be customized.
>>
>> On Tue, Jun 9, 2015 at 3:00 PM, Marco Massenzio <[email protected]>
>> wrote:
>>
>>> Hadn't realized that the mailing list forwarder would make the images
>>> unavailable, apologies about that.
>>>
>>> I've created this Google Doc
>>> <https://docs.google.com/document/d/1KQIyEzFP3LF05FkW81SYcG50-HaACD2u-f2SPVAERI8/edit>
>>> which should be open and accessible.
>>>
>>> Again, please let me know if anyone feels strongly that we should keep
>>> the current workflow.
>>> Thanks!
>>>
>>> *Marco Massenzio*
>>> *Distributed Systems Engineer*
>>>
>>> On Tue, Jun 9, 2015 at 2:26 PM, Marco Massenzio <[email protected]>
>>> wrote:
>>>
>>>> Folks,
>>>>
>>>> Please take a look at MESOS-2806: in a nutshell, our current workflow
>>>> is rather convoluted and brings about a host of issues, when managing
>>>> tasks' status transitions (detailed in the Jira - see screenshots there).
>>>>
>>>> This is what it currently looks like:
>>>>
>>>> [image: Inline image 1]
>>>>
>>>> (spaghetti workflow? :)
>>>>
>>>> I would propose to simplify it to the following:
>>>>
>>>> [image: Inline image 2]
>>>>
>>>> I'm sure we can think up all sorts of corner cases, but I would submit
>>>> that simplicity would trump complexity and allow us to track progress (or
>>>> lack thereof) of stories/tasks/bugs in a much more punctual manner.
>>>>
>>>> Anyone against it?
>>>>
>>>> *Marco Massenzio*
>>>> *Distributed Systems Engineer*
>>>>
>>>
>>>
>>
>

Reply via email to