Closed
      
        Bug 794217
      
      
        Opened 13 years ago
          Closed 11 years ago
      
        
    
  
Set up B2G filesystem image diffs for updates
Categories
(Release Engineering :: General, defect, P3)
Tracking
(blocking-basecamp:-)
        RESOLVED
        INCOMPLETE
        
    
  
| blocking-basecamp | - | 
People
(Reporter: overholt, Unassigned)
Details
(Whiteboard: [b2g][updates])
Assuming I'm understanding the plan correctly, we're going to need to have binary diffs of the B2G filesystem to use for updates.  These will be generated differently than current Firefox diffs.
|   | ||
| Updated•13 years ago
           | 
Priority: -- → P3
Whiteboard: [b2g][updates]
|   | ||
| Comment 1•13 years ago
           | ||
mwu has been working on improving our binary diffing for b2g, CCing him here as well.
| Comment 2•13 years ago
           | ||
Marshall, have you seen build/tools/releasetools/ota_from_target_files ? It looks like it can generate incremental FOTA updates for us.
| Reporter | ||
| Comment 3•12 years ago
           | ||
Are we going to do incremental diffs for v1?
Flags: needinfo?(catlee)
| Reporter | ||
| Comment 5•12 years ago
           | ||
(In reply to Chris AtLee [:catlee] from comment #4)
> Not AIUI.
Okay, then I don't think this should block v1.  Please re-nom if we need this.
blocking-basecamp: ? → -
|   | ||
| Updated•12 years ago
           | 
Assignee: catlee → nobody
|   | ||
| Updated•12 years ago
           | 
No longer blocks: b2g-fota-updates
| Comment 6•12 years ago
           | ||
Is this bug still relevant/useful?
| Reporter | ||
| Comment 7•12 years ago
           | ||
Not for now AFAIK.
| Assignee | ||
| Updated•12 years ago
           | 
Product: mozilla.org → Release Engineering
| Updated•11 years ago
           | 
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
          You need to log in
          before you can comment on or make changes to this bug.
        
Description
•