Difference between revisions of "User:Alsroot/trash/Object Bundles"
(→Scope) |
|||
| Line 64: | Line 64: | ||
* [[Unified Bundles]] | * [[Unified Bundles]] | ||
* [http://wiki.laptop.org/go/Journal_entry_bundles Journal entry bundles] | * [http://wiki.laptop.org/go/Journal_entry_bundles Journal entry bundles] | ||
| + | * [http://wiki.laptop.org/go/Bundle_concepts Bundle concepts] | ||
== Release Notes == | == Release Notes == | ||
Revision as of 18:45, 21 July 2009
Summary
Package Journal objects to bundles to preserve sugar related metadata.
Owner
- Name: Aleksey Lim
- Email: send an email
Current status
- Targeted release: 0.86
- Last updated: Tue Jul 21 02:18:17 UTC 2009
- Percentage of completion: 0%
Detailed Description
- Fix issues related to name mangling of Journal objects after uploading/downloading
- Keep objects DS metadata while transfering between user-server-user
- we can package DS object to bundles (it relates to Unified Bundles)
Benefit to Sugar
Let users export/import Journal objects.
Scope
- deprecate .xol bundles
- deprecate .xoj bundles
- provide unified format for metadata file in .xo bundles which should support
- activities, former .xo bundles (0.88)
- libraries, former .xol bundles (0.86)
- journal entries, former .xoj bundles (0.86)
- make Browse upload object bundles when the server says so
- InfoSlicer generates object bundles in 0.86 environment
How To Test
- Create a new TurtleArt activity
- Upload the new entry to the SL wiki using Browse
- Use Browse to download the entry back to Journal
- Resume it from Journal
User Experience
If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.
Dependencies
Fructose dependencies.
Contingency Plan
None necessary, revert to previous release behaviour.
Documentation
Release Notes
The Sugar Release Notes inform end-users about what is new in the release. An Example is 0.84/Notes. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.