9.1.0 requirements: Difference between revisions
No edit summary |
|||
| Line 16: | Line 16: | ||
This section outlines the main areas of technology that we will focus on improving. All of the specific features should address one of these primary concerns. The choice of these comes from listening to users and deployment leads and hearing what their concerns. |
This section outlines the main areas of technology that we will focus on improving. All of the specific features should address one of these primary concerns. The choice of these comes from listening to users and deployment leads and hearing what their concerns. |
||
The |
The strategic priorities are focused on making the XO work the way users expect it to and helping get the XO deployed more quickly in more countries. |
||
== Greater reliability and performance == |
== Greater reliability and performance == |
||
| Line 31: | Line 31: | ||
# Updating activities |
# Updating activities |
||
# Activation and Leases |
# Activation and Leases |
||
Each should be optimized for case where XS is available, Internet only available and no Internet (AKA USB). Must make it easier to load new image, latest translations, activities and content bundles. |
|||
== Collaboration == |
|||
# More fully defined activity sharing paradigms, especially with write. |
|||
# At least one data collection and analysis application supported with an architecture defined for others to follow. |
|||
# Easier file sharing between XOs and easier to generate and upload user generated content to the internet. |
|||
# Workflow defined and tools developed for students to collaborate on projects. Must also maintain a history of projects and people who worked on them |
|||
# Greater scale for number of XOs that can collaborate. |
|||
# Segregate users so that all the available channels and spectrum are used. |
|||
= Pedagogical strategy = |
|||
.... |
|||
= Primary release drivers = |
= Primary release drivers = |
||
Revision as of 14:47, 2 December 2008
This page defines the requirements for release 9.1.0. It is modeled after a Product Requirements Definition document which intends to define who the users are, what they need and what technology should be built in order to achieve the product and user goals.
Feature requests tracks features, requirements, and requests, and plans by customer; Feature roadmap tracks software features by technical strategy.
See also idea plans for upcoming technical conference at: XOcamp 2
Overview
This release is the first major new feature release after 8.2.0 Its is the first of two major feature releases we want to deliver in 2009. The target date for this release is March 7, 2009 (Note: date and feature set not final and subject to change).
This release must run on C1, C2, C3 and the new C4 motherboards. (check exact list and add URL)
Technical strategy
This section outlines the main areas of technology that we will focus on improving. All of the specific features should address one of these primary concerns. The choice of these comes from listening to users and deployment leads and hearing what their concerns.
The strategic priorities are focused on making the XO work the way users expect it to and helping get the XO deployed more quickly in more countries.
Greater reliability and performance
- No loss of data. Fewer crashes and fewer open bugs than 8.2 and previous releases. See also: http://wiki.laptop.org/go/User:Gregorio/8.2.0_release_criteria
- At the time of the release, works the way the manual says it works. That is, all of the things explained and listed in these manuals must work as described.
- Better performance includes faster GUI interactions. Includes launching activities, switching from one activity to another, using the journal and using the frame. GUI, activities, back ups.
Easier to deploy and maintain
Quick, clean way to upgrade XOs in the field. Covers several cases including
- Creating customization images (to include language packs and rpms)
- Installing images in the warehouse
- Upgrade in the schools
- Updating activities
- Activation and Leases
Primary release drivers
Date:
The goal (not confirmed) is to release at the end of Q1 (March 2009).
Customers
Schools that will be deploying in Aug-Sept of 2009.
Features
Target deployments
See: Deployments
Standard information
(These are all semantic annotations that other pages such as Releases can query.)
Status: status::gathering requirements and setting priorities
Primary maintainer: not chosen yet
ECO: not yet
Primary objectives:
- [[Has objective::This is a time-based release per the process at: Release Process Home.]]
- Has objective::Not chosen yet.
The process is not final. It is a set of rough guidelines still being worked out and subject to change.
Lead customer: ?
Build number and URL: Build number::999
Schedule: Signed and final image available for download and new XOs built with 9.1.0 in manufacturing by Target date::March 15, 2009