Folks,
thanks to Tony Stevenson in INFRA, our Mesos workflow
https://issues.apache.org/jira/secure/attachment/12740454/Mesos%20Workflow.png
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
Hey Marco,
Thanks for doing this!
+1 removing “closed”
+1 to go back from “Reviewable” to “In Progress”
+1 to go from “In Progress” to “Accepted” instead of “Open”
+1 Removing “Reopened
On 09 Jun 2015, at 23:26, Marco Massenzio ma...@mesosphere.io wrote:
Folks,
Please take a look at
+1 to removing Closed. In other projects, I've seen Resolved mean that a
supposed fix has been committed, and Closed means that somebody (QA?
Reporter?) has verified the fix, but we don't wait for verification, so
it's probably pointless for us.
+1 to removing Reopened, and just going back to
For the ASF Jira we do not allow special permissions for customizing or
changing settings, we have been down that road before and it turned into a
mess. There are some settings within the ASF Jira which are global to all
projects and can not be changed, but you can have a custom workflow and
Very helpful Marco… I like the idea of tightening our JIRA workflow.
+1 removing “closed
+1 “reviewable” back to in progress — to me this is a very helpful signal for
longer lasting comment addressing
+1 making sure that “accepted is the gatekeeper and includes assigning the
maintainer as a
+1 This sounds great to me Marco. I love eliminating Reopened, as well as
simplifying (constraining) other transitions. I couple of quick questions:
Why does stoping progress go from In Progress back to Open instead of
Accepted? Seems like it's still an Accepted issue just not being worked on.
Inline...
On Tue, Jun 9, 2015 at 4:56 PM, Benjamin Mahler benjamin.mah...@gmail.com
wrote:
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
Thanks, everyone, for your suggestions: quick feedback was much appreciated!
I've updated the Google Doc, I think we're in good shape, I'll wait until
Friday to hear if anyone has still objections, then I'll work with Jake
(thanks for offer to help!) to implement it.
*Marco Massenzio*
On Wed, Jun 10, 2015 at 1:15 AM, Till Toenshoff toensh...@me.com wrote:
Very helpful Marco… I like the idea of tightening our JIRA workflow.
+1 removing “closed
done
+1 “reviewable” back to in progress — to me this is a very helpful
signal for longer lasting comment addressing
done
+1
inline...
On Tue, Jun 9, 2015 at 11:29 PM, Benjamin Hindman b...@eecs.berkeley.edu
wrote:
+1 This sounds great to me Marco. I love eliminating Reopened, as well as
simplifying (constraining) other transitions. I couple of quick questions:
Why does stoping progress go from In Progress back to
inline...
On Wed, Jun 10, 2015 at 12:44 AM, Adam Bordelon a...@mesosphere.io wrote:
+1 to removing Closed. In other projects, I've seen Resolved mean that a
supposed fix has been committed, and Closed means that somebody (QA?
Reporter?) has verified the fix, but we don't wait for
To go from accepted to open you need to go through in progress?
On Wed, Jun 10, 2015 at 2:16 PM, Marco Massenzio ma...@mesosphere.io
wrote:
Thanks, everyone, for your suggestions: quick feedback was much
appreciated!
I've updated the Google Doc, I think we're in good shape, I'll wait until
Don't forget that folks accidentally do things all the time in JIRA, so if
you fence off the ability to go back you make an accident permanent, or
does JIRA have some undo support I'm unaware of?
On Wed, Jun 10, 2015 at 6:33 PM, Marco Massenzio ma...@mesosphere.io
wrote:
On Wed, Jun 10, 2015 at
On Wed, Jun 10, 2015 at 6:44 PM, Benjamin Mahler benjamin.mah...@gmail.com
wrote:
Don't forget that folks accidentally do things all the time in JIRA,
or in life :)
eh eh I never forget that
so if
you fence off the ability to go back you make an accident permanent, or
does JIRA have some
On Wed, Jun 10, 2015 at 6:19 PM, Benjamin Mahler benjamin.mah...@gmail.com
wrote:
To go from accepted to open you need to go through in progress?
That part wasn't changed from before?
Anyways, why would you ever want to do that?
This means that, at some point we looked at something, thought
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
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
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:
+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
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
20 matches
Mail list logo
