mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benjamin Mahler <benjamin.mah...@gmail.com>
Subject Re: [jira] [Updated] (MESOS-1280) Add replace task primitive
Date Fri, 15 May 2015 00:31:29 GMT
Well, we just want the commit message when a ticket is resolved via a
change, whoever resolves it (usually the committer is in the best position
to do all of these when the commits are pushed). Ideally the tooling does
it for them when they apply the review and push it, so yes, help us improve
the tooling! :)

On Thu, May 14, 2015 at 4:28 PM, Michael Park <mcypark@gmail.com> wrote:

> Hey Ben,
>
> Looks like I used to close tickets in the past before I learned that I
> should resolve them.
> I've added the commit messages to the tickets also, but my understanding
> was that the committer does that when after they commit. Could you clarify
> what the expectation is for that?
>
> Also, I think it might be worth putting in some effort to remove this
> process of manually linking between between JIRA tickets, review requests,
> and commits.
> With *post-reviews.py* at least we get the link from the commit to the
> review request for free, but the rest of them are still manually linked...
>
>    - JIRA ticket -- *manual* --> review request
>    - JIRA ticket -- *manual* --> commit
>    - review request -- *manual* --> JIRA ticket
>    - review request -- *missing* --> commit (gotta go through review
>    request -> JIRA ticket -> commit, this path is probably good enough)
>    - commit -- *missing* --> JIRA ticket (gotta go through commit ->
>    review request -> JIRA ticket. *this is painful if we're trying to
>    figure out which commit fixed a JIRA ticket*)
>    - commit -- auto (with *post-reviews.py*) --> review request
>
> Anyway, just some thoughts.
>
> MPark.
>
> On 14 May 2015 at 14:16, Benjamin Mahler <benjamin.mahler@gmail.com>
> wrote:
>
>> Try to use "Resolved" instead of "Closed" if it was fixed / taken care
>> of, etc. Also, with Resolved you don't need to re-open to make certain
>> changes.
>>
>> On Wed, May 13, 2015 at 6:01 PM, Michael Park <mcypark@gmail.com> wrote:
>>
>>> For the tickets that I was involved in:
>>>
>>> The following tickets were open, so I went ahead and updated the type.
>>>
>>> https://issues.apache.org/jira/browse/MESOS-2475
>>> <http://goog_705696099>
>>> https://issues.apache.org/jira/browse/MESOS-2476
>>> <http://goog_705696099>
>>> https://issues.apache.org/jira/browse/MESOS-2477
>>> <http://goog_705696099>
>>> https://issues.apache.org/jira/browse/MESOS-2139
>>> <http://goog_705696099>
>>> https://issues.apache.org/jira/browse/MESOS-2658
>>>
>>> The following tickets are closed, so I'm not sure if I should re-open
>>> them only to re-close them with a different type.
>>> Perhaps someone with a magic button can update these tickets' type to
>>> *Task*?
>>>
>>> https://issues.apache.org/jira/browse/MESOS-2263
>>> <http://goog_705696102>
>>> https://issues.apache.org/jira/browse/MESOS-2265
>>> <http://goog_705696102>
>>> https://issues.apache.org/jira/browse/MESOS-2264
>>> <http://goog_705696102>
>>> https://issues.apache.org/jira/browse/MESOS-2266
>>>
>>> Thanks,
>>>
>>> MPark.
>>>
>>>
>>> On 13 May 2015 at 17:13, Benjamin Mahler <benjamin.mahler@gmail.com>
>>> wrote:
>>>
>>>> Thanks for clarifying Jake! Marco / Ben, can you guys audit the "type"
>>>> of
>>>> the tickets that were mass transitioned to bugs? Many of these are not
>>>> bugs
>>>> :(
>>>>
>>>> On Wed, May 13, 2015 at 12:54 PM, Marco Massenzio <marco@mesosphere.io>
>>>> wrote:
>>>>
>>>> > +benh - who can explain the rationale.
>>>> >
>>>> > *Marco Massenzio*
>>>> > *Distributed Systems Engineer*
>>>>
>>>> >
>>>> > On Wed, May 13, 2015 at 12:06 PM, Jake Farrell <jfarrell@apache.org>
>>>> > wrote:
>>>> >
>>>> >> Hey Ben
>>>> >> Yes, subtasks and technical tasks where removed from the Mesos
>>>> project in
>>>> >> jira per an infra ticket requesting this. These all had to be hand
>>>> edited
>>>> >> as jira does not allow bulk editing of subtasks so all subtasks
>>>> where run
>>>> >> though and in the process they where converted to issues with the
>>>> default
>>>> >> issue type of 'bug'.
>>>> >>
>>>> >> -Jake
>>>> >>
>>>> >> On Wed, May 13, 2015 at 12:54 PM, Benjamin Mahler <
>>>> >> benjamin.mahler@gmail.com
>>>> >> > wrote:
>>>> >>
>>>> >> > +jake
>>>> >> >
>>>> >> > We received a large number of emails about ticket transitions.
It
>>>> looks
>>>> >> > like they were all subtasks that were mass converted to bugs?
Many
>>>> of
>>>> >> these
>>>> >> > are not "bugs", e.g. this one, so I'm curious what caused this?
>>>> Were
>>>> >> > subtask tickets disabled for the mesos project?
>>>> >> >
>>>> >> > ---------- Forwarded message ----------
>>>> >> > From: Jake Farrell (JIRA) <jira@apache.org>
>>>> >> > Date: Tue, May 12, 2015 at 8:17 PM
>>>> >> > Subject: [jira] [Updated] (MESOS-1280) Add replace task primitive
>>>> >> > To: issues@mesos.apache.org
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> >      [
>>>> >> >
>>>> >>
>>>> https://issues.apache.org/jira/browse/MESOS-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>>>> >> > ]
>>>> >> >
>>>> >> > Jake Farrell updated MESOS-1280:
>>>> >> > --------------------------------
>>>> >> >     Issue Type: Bug  (was: Sub-task)
>>>> >> >         Parent:     (was: MESOS-938)
>>>> >> >
>>>> >> > > Add replace task primitive
>>>> >> > > --------------------------
>>>> >> > >
>>>> >> > >                 Key: MESOS-1280
>>>> >> > >                 URL:
>>>> https://issues.apache.org/jira/browse/MESOS-1280
>>>> >> > >             Project: Mesos
>>>> >> > >          Issue Type: Bug
>>>> >> > >          Components: c++ api, master, slave
>>>> >> > >            Reporter: Niklas Quarfot Nielsen
>>>> >> > >
>>>> >> > > Also along the lines of MESOS-938, replaceTask would one
of a
>>>> couple
>>>> >> of
>>>> >> > primitives needed to support various task replacement and scaling
>>>> >> > scenarios. This replaceTask() version is significantly simpler
>>>> than the
>>>> >> > first proposed one; it's only responsibility is to run a new
task
>>>> info
>>>> >> on a
>>>> >> > running tasks resources.
>>>> >> > > The running task will be killed as usual, but the newly
freed
>>>> >> resources
>>>> >> > will never be announced and the new task will run on them instead.
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> > --
>>>> >> > This message was sent by Atlassian JIRA
>>>> >> > (v6.3.4#6332)
>>>> >> >
>>>> >> >
>>>> >>
>>>> >
>>>> >
>>>>
>>>
>>>
>>
>

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