+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
Thank you for replying and for opening a ticket. I also added a ticket
related to the issue: https://issues.apache.org/jira/browse/MESOS-2820
Should I close it?
Thank you
2015-06-10 0:29 GMT+02:00 Niklas Nielsen nik...@mesosphere.io:
Thanks Alberto - I finally got to look at the trace and
+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.
Mark it as a duplicate.
On 10 Jun 2015 8:21 am, Alberto Rodriguez ardl...@gmail.com wrote:
Thank you for replying and for opening a ticket. I also added a ticket
related to the issue: https://issues.apache.org/jira/browse/MESOS-2820
Should I close it?
Thank you
2015-06-10 0:29 GMT+02:00
Done! Thank you!
2015-06-10 8:52 GMT+02:00 Alex Rukletsov a...@mesosphere.com:
Mark it as a duplicate.
On 10 Jun 2015 8:21 am, Alberto Rodriguez ardl...@gmail.com wrote:
Thank you for replying and for opening a ticket. I also added a ticket
related to the issue:
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
Hi Mesos friends,
We need your help promoting the #MesosCon diversity scholarship.
#MesosCon, the annual open source #ApacheMesos developers conference, is
now accepting applications for their diversity scholarship. It provides
financial assistance for women (cis and trans), genderqueer people,
Good news, everyone:
We’ve expanded the MesosCon program (http://mesoscon.org) to add
lightning talks: 5-minute presentations for speakers to introduce a
project they’re working on, or share an idea related to Mesos. Lightning
talks will take place during lunchtime of the conference, which takes
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
Hey Oliver,
thanks for the patch and really glad to hear that Mesos just works for
you!
As you can imagine, we'd love to add Uber to the Powered by page:
http://mesos.apache.org/documentation/latest/powered-by-mesos/
Do you think that would be possible?
Welcome to the club!
*Marco Massenzio*
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
Yup, please do.
On Wed, Jun 10, 2015 at 5:08 PM, Marco Massenzio ma...@mesosphere.io
wrote:
Hey Oliver,
thanks for the patch and really glad to hear that Mesos just works for
you!
As you can imagine, we'd love to add Uber to the Powered by page:
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
20 matches
Mail list logo
