#7426 BLOC 8.2.0 (: Journal in f7 disappears after olpc-update to f9

[Zarro Boogs per Child]

#7426: Journal in f7 disappears after olpc-update to f9
-------------------------+--------------------------------------------------
   Reporter:  mikus      |       Owner:  tomeu                            
       Type:  defect     |      Status:  reopened                         
   Priority:  blocker    |   Milestone:  8.2.0 (was Update.2)             
  Component:  datastore  |     Version:  Development build as of this date
 Resolution:             |    Keywords:  blocks:8.2.0 8.2.0:?             
Next_action:  code       |    Verified:  0                                
  Blockedby:             |    Blocking:                                   
-------------------------+--------------------------------------------------

Comment(by dgilmore):

 the way booting into the alt image works is that we have two images
 installed so we use an additional ~300mb on the nand, the question of
 different versions collaborating is not unrelated, if only some machines
 get updated. they could be over the wire api changes that cause issues.
  Option 1, test cost is not high, the only cost is to document that
 journal is not backwards compatible. (backups are important here, likely
 you can restore a backup and get back the old journal)
  Option 2, maintenance cost is extremely high, if we hit a bug that we
 need upstream help with. the first thing they will ask is to test with the
 latest version. and will likely not help patch the older version. moving
 forward long term cost only gets higher. by not moving forward you are
 setting us up to never move forward.
  Option 3 - booting into the alt-os image can cause all sorts of other
 issues, especially if activites were updated and only work with the newer
 sugar. sugar would need to know how to do some kind of dump restore to get
 the data into the alt-os image likely we would need to do something to
 track activities and allow for multiple versions of activities to be
 installed, and provide some way to detect what can be used safely in a
 particular build.
  alt-boot really should only be an option for developers. we should not be
 shipping updates that have issues that would want to have deployments alt-
 boot into the old os. its a great safety net if a test build fails to even
 boot.
  To give the kids the most amount of nand possible for user data they
 should get reflashed not updated. and then have there datastore restored
 from backup.

-- 
Ticket URL: <http://dev.laptop.org/ticket/7426#comment:15>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system