+benh - who can explain the rationale. *Marco Massenzio* *Distributed Systems Engineer*
On Wed, May 13, 2015 at 12:06 PM, Jake Farrell <jfarr...@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.mah...@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) <j...@apache.org> > > Date: Tue, May 12, 2015 at 8:17 PM > > Subject: [jira] [Updated] (MESOS-1280) Add replace task primitive > > To: iss...@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) > > > > >
