0.84/0.83.1 Notes: Difference between revisions
| Line 70: | Line 70: | ||
=== sugar-datastore === | === sugar-datastore === | ||
* The datastore has been rewritten, to simplify and improve maintainability. As a first step the API was not changed at all (other than removing removable devices support), so that the new implementation was swapped in without changes to activities and Sugar | * The datastore has been rewritten, to simplify and improve maintainability. As a first step the API was not changed at all (other than removing removable devices support), so that the new implementation was swapped in without changes to activities and Sugar | ||
* Drop for now the management of removable devices inside the DS. Removable devices support in Sugar should happen without intervention from the DS | * Drop for now the management of removable devices inside the DS. Removable devices support in Sugar should happen without intervention from the DS | ||
* #8155 The datastore should hard link identical files, to handle repeated downloads of the same content without filling up NAND | * #8155 The datastore should hard link identical files, to handle repeated downloads of the same content without filling up NAND | ||
* Support arbitrary metadata properties that activities wish to add #4662 | * Support arbitrary metadata properties that activities wish to add #4662 | ||
* Degrade gracefully if a database gets corrupted- Basic functionality should only depend on the filesystem being available. Any other data structures (full text index) should be rebuildable from the filesystem | * Degrade gracefully if a database gets corrupted- Basic functionality should only depend on the filesystem being available. Any other data structures (full text index) should be rebuildable from the filesystem #6269 | ||
=== sugar-presence-service === | === sugar-presence-service === | ||