#8147 NORM 9.1.0: journal should stop using the property "mtime"

[Zarro Boogs per Child]

#8147: journal should stop using the property "mtime"
------------------------------+---------------------------------------------
 Reporter:  tomeu             |         Owner:  tomeu             
     Type:  defect            |        Status:  new               
 Priority:  normal            |     Milestone:  9.1.0             
Component:  journal-activity  |       Version:  Git as of bug date
 Keywords:                    |   Next_action:  code              
 Verified:  0                 |     Blockedby:                    
 Blocking:                    |  
------------------------------+---------------------------------------------
 In the beginnings of the Journal development we were storing the
 modification time of entries in a datetime format without the timezone.
 This caused problems when the time zone of the system was changed, because
 we didn't knew any more if one entry would be more recent than another,
 thus we couldn't sort and filter correctly.

 Around Sept 2007 we added the timestamp property and started using it
 instead of mtime for displaying the age of entries. But we couldn't drop
 mtime completely because some ongoing trials were using the older software
 and would want to update to more recent versions without losing their
 data.

 Thus we have been displaying the timestamp property but we have had to
 keep filtering and sorting by the mtime property because we cannot
 fallback in those cases to another property. This can cause problems when
 the user changes the timezone, as some entries will appear as incorrectly
 sorted around the moment when the timezone was changed.

 Today we can finally drop mtime because we are not supporting any more
 upgrades from pre-ship2 releases. Thus I think that in the next major
 release after 8.2.0 we should drop definitely the mtime property.

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