Closed Bug 794216 Opened 12 years ago Closed 9 years ago

Decide and document how many B2G filesystem diffs we keep for updates

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(blocking-basecamp:-)

Status:
RESOLVED WONTFIX
Project Flags:
blocking-basecamp -

People

(Reporter: overholt, Assigned: clee)

Details

Before we can do incremental updates for B2G with binary diffs, we'll need to decide how many diffs we want to retain.
Are we going to do incremental diffs for v1?
Flags: needinfo?(clee)
I think cjones might have the details.
Flags: needinfo?(clee) → needinfo?(jones.chris.g)
cjones, any update here?
Sorry, missed the ping in comment 2. Yes, incremental updates are table stakes in v1 markets. There are no current plans for Mozilla to build these ourselves so the topic of this bug isn't a blocking issue atm.
Flags: needinfo?(jones.chris.g)
As per cjones' comment
blocking-basecamp: ? → -
Is this bug still relevant?
Not for now AFAIK.
Product: mozilla.org → Release Engineering
Whiteboard: kanbanzilla[Needs Investigation]
Whiteboard: kanbanzilla[Needs Investigation]
This bug is way out of date, lots of things have probably changed. Lets start fresh if we need to.
Status: NEW → RESOLVED
Closed: 9 years ago
QA Contact: mshal
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.