Feature #8816

Investigate upload mechanisms and reactivity for browser app stores

Added by sajolida 2015-01-28 17:46:34 . Updated 2015-02-21 18:46:49 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Installation
Target version:
Start date:
2015-01-28
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Subtasks

History

#1 Updated by sajolida 2015-01-28 17:47:26

  • Subject changed from Compare reactivity of upgrade mechanism in app stores (browser and OS) to Compare reactivity of upgrade mechanism in app stores (Firefox, Chrome, Windows, Mac)

#2 Updated by sajolida 2015-02-04 17:10:23

  • Subject changed from Compare reactivity of upgrade mechanism in app stores (Firefox, Chrome, Windows, Mac) to Investigate upload mechanisms and reactivity for browser app stores
  • Category set to Installation
  • Parent task deleted (Feature #8583)

#3 Updated by sajolida 2015-02-04 17:10:40

  • Priority changed from Elevated to Normal
  • Parent task set to Feature #8849

#4 Updated by sajolida 2015-02-04 17:13:29

  • Who would upgrade the extension to the app stores?
  • How often?
  • What happens if the signing key changes or is revoked?

#5 Updated by sajolida 2015-02-05 21:26:11

  • Priority changed from Normal to Elevated

#6 Updated by sajolida 2015-02-21 18:46:50

  • Status changed from Confirmed to Resolved
  • Assignee deleted (sajolida)
  • In Firefox, it has to go through a manual review process that can take several days.
  • In Chrome, it can be uploaded directly to the store by us.