Feature #15888

Analyze the development cost of tickets related to #14544

Added by sajolida 2018-08-31 11:39:41 . Updated 2019-01-23 13:58:34 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_3.12
Start date:
2018-08-31
Due date:
% Done:

100%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Subtasks

Related issues

Blocks Tails - Feature #15507: Core work 2019Q1: Foundations Team Resolved 2018-04-08

History

#1 Updated by intrigeri 2018-11-17 18:08:56

  • Target version changed from Tails_3.12 to Tails_3.13

#2 Updated by intrigeri 2018-11-17 18:11:20

#3 Updated by intrigeri 2018-11-17 18:27:14

  • Assignee changed from intrigeri to sajolida
  • QA Check set to Info Needed

There are already 46 tickets there, we keep adding more (I count 18 since the summit), and sajolida also needs to go through this list as well for Feature #15887, so I wonder if there’s a more efficient way to proceed than each of us separately going through all these tickets: if we really need to do that, I’ll only be able to give extremely rough estimates even if I spend “only” ~10 hours on it. I know that we need all this data to compute cost/benefit numbers but still.

So, for this first batch, maybe we can do a first quick triaging pass together, spending 3 min max on each ticket, in order to identify those that quite obviously have a particularly bad or good cost/benefit. That will already take a few hour if we have 60 tickets to go through. Then we can focus, each on our side, on those that seem to have a particularly good cost/benefit, and perhaps we’ll get enough data to bootstrap this process. And if that’s not enough, well, we’ll have to dive into the rest of the tickets. What do you think? I would schedule this in 2019Q1.

Also, at the summit we decided to do that before the end of the year in order to have some data for our budget forecasting, which we then postponed by 3 months => postponing this as well.

#4 Updated by sajolida 2018-12-06 19:26:29

  • Assignee changed from sajolida to intrigeri

We didn’t specified how detailed we wanted these value/cost analysis to be but I clearly don’t think it’s worth spending tens of hours on them, but rather a couple of minutes on each ticket as a first pass.

If you think that doing this together would make things easier, then let’s do this!

#5 Updated by intrigeri 2018-12-07 09:40:25

> We didn’t specified how detailed we wanted these value/cost analysis to be but I clearly don’t think it’s worth spending tens of hours on them, but rather a couple of minutes on each ticket as a first pass.

We’re on the same page. That’ll already take a few hours.

> If you think that doing this together would make things easier, then let’s do this!

Nice, I’ll send you scheduling proposals privately.

#6 Updated by intrigeri 2018-12-07 09:46:32

  • QA Check deleted (Info Needed)

#7 Updated by intrigeri 2019-01-23 09:30:47

  • Target version changed from Tails_3.13 to Tails_3.12

First round happens today.

#8 Updated by intrigeri 2019-01-23 13:58:34

  • Status changed from Confirmed to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 0 to 100