Bug #12127

Make "notes" more structured in the description of our mirror pool

Added by sajolida 2017-01-10 18:38:57 . Updated 2018-01-16 13:41:01 .

Status:
Confirmed
Priority:
Low
Assignee:
sajolida
Category:
Infrastructure
Target version:
Start date:
2017-01-10
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

So we’ve been using the “notes” field in our JSON schema for at least two different things very recurrently:

  • URL of stats (8 times right now), so maybe having a dedicated “stats”
    string would be cool.
  • Failures, with a date and a description. Most of the time we
    only keep the latest failure. Sometimes we keep two (see
    https://tails.unixcorn.org/tails/). So maybe this deserves a
    dedicated field as well. It could be a string called “disabled_because”.

Having these two out of the way would tidy up most of the things.

I want to try to implement this and learn a bit of JSON on the way.

Subtasks

Related issues

Related to Tails - Feature #14922: Integrate download metrics in the new download page Resolved 2017-11-04

History

#1 Updated by Anonymous 2018-01-16 13:41:01

I think I agree with the “stats”. However, I think we should keep this file simple, and add in “notes” something like “last_failure” $DATE & “failed_times” $incremental number but without creating a dedicated field. Otherwise we might also include this info in our Git commit messages instead.

#2 Updated by sajolida 2018-01-21 11:23:52

  • related to Feature #14922: Integrate download metrics in the new download page added