mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marco Massenzio <>
Subject Re: Mesos Jira workflow
Date Fri, 26 Jun 2015 00:02:43 GMT

thanks to Tony Stevenson in INFRA, our Mesos workflow
now reflects the one we arrived at.

Due to some quirks in Jira, the transitions buttons shown at the top of the
issue may not always reflect a valid transition (we're looking into this
with Tony): for example, an Accepted story has a "Stop Progress" button
(makes no sense); if you hit it, you'll get an error message - which is
correct, but annoying (also, really, we would like a "Start Progress"

For the time being, please use the "Workflow" button (which offers a subset
of possible states to transition to) to move Issues across states.

We'll keep you updated on progress.
The INFRA ticket to follow is here:

*Marco Massenzio*
*Distributed Systems Engineer*

On Tue, Jun 9, 2015 at 2:26 PM, Marco Massenzio <> 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*

  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message