9.1.0 requirements

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.
  

http://www.laptop.org/manual/

• 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

Easier to deploy focuses on facilitating the imaging of XOs, their activation, the installation and extension of custom leases and anything else needed to get the XOs from the factory in to the schools. Some examples include:

1. Creating customization images (to include language packs and rpms)
2. Installing images in the warehouse
3. Activation and Leases

Easier to maintain focuses on upgrading, keeping the XOs working, monitoring them and allowing recovery of data from errors. Some examples include:

1. Upgrade in the schools
2. Updating activities
3. Reducing power consumption

Primary release drivers

Date: March 7, 009

Customers: Rwanda, Peru, Ethiopia, Uruguay, Haiti, Birmingham

Features

The following are critical must deliver features for this release. They are listed in priority order.

1. Rebasing on F10 and allowing "regular" Fedora window managers and applications to run. http://wiki.laptop.org/go/Feature_roadmap#Rebase_on_Fedora_10
2. Activation/lease/signing/image customization http://wiki.laptop.org/go/Feature_roadmap#Security.2C_activation_and_deployability
3. Power management http://wiki.laptop.org/go/Feature_roadmap#Power_management
4. Localization/translation http://wiki.laptop.org/go/Feature_roadmap#Localization

Further definition of each feature and tagging of related sub-features will happen in December, 2008.

Activities

Sign in to the wiki and leave your suggestion for any activities you think we should install by default here.

Each activity will need a version, a test case (http://wiki.laptop.org/go/Test_cases) and a maintainer to be considered for the release.

The maintainer is the Property:Contact person on the activity's wiki page (click [Edit with form] and modify "Maintainer's user page" to update), and the .xo URL and version for 9.1.0 should be in the activity's Activities/My activity_(latest) fragment, e.g. Activities/Chat_(latest)

Default Activities for 9.1.0

Name	URL to .XO file	Version	Documentation	Maintainer	URL to Test Case	License status	Status	Comments
Chat	http://dev.laptop.org/~morgan/bundles/Chat-60.xo	60	Chat	Morgan		GPLv2+	Accepted pending final tests.

Please help add all potential activities to this table. Add as much info as you have and leave the rest blank.

Lists of candidate activities

• All activity pages that have Activity group Activities/G1G1 checked:

{{#ask: Activity group::Activities/G1G1 | format = list}}

• The list below was pasted from the test pages:

Analyze

Browse
Calculate
Clock
Color
Comic
Distance
Etoys
Gcompris-Chess
Gcompris-Sudoku
Help
Implode
Log
Maze
Measure
Memorize
Moon
Paint
Pippy
Read
Record
TurtleArt

x2o

• The full set of OLPC hosted activities at Activities
• See Activity queries for a sortable list of everything in Category:Activities.
• a previous listing of activities and status on Google (Matrix deprecated tab) at http://spreadsheets.google.com/ccc?key=p_Xhb6KcXLyEViA50CnCaDg&hl=en

Nominations

(sign your nominations with -- ~~~~)

• I nominate Develop. Version and test case upcoming. Homunq 15:04, 10 December 2008 (UTC)

• I nominate StarChart (http://www.wa1gsf.net/downloads/XO/StarChart-5.xo) version 5 maintained by David Wallace, licensed under GPLv2+. Note that Version 6 is in development and will have 2 more features and should be i18n-ed. Release of v.6 is planned for 1/1/09. -- Davewa 19:39, 10 December 2008 (UTC)

Schedule

• December 5 - Agree and document on Trac usage. Tag critical features for 9.1.0 on roadmap page and linked on 9.1.0 page.
• December 12 - Trac scrub underway bugs targeted for inclusion in 9.1.0 flagged. First pass at requirements definition done for all main features.
• December 19 - Scrub of all past Trac bugs completed. Last round of comments on requirements. First pass at specification write ups. Rough scoping recorded and engineers assigned.
• December 24 - Branch strategy defined and check in branch chosen (Joyride?). Weekly bug triage begun.
• January 7 - Presentations for XO Camp shared. All specifications posted and reviews scheduled. Code reviews scheduled as needed. Designs of major features shared with key customers for confirmation and comment.
• January 12 to 15 - XO Camp held. http://wiki.laptop.org/go/XOcamp_2.
• January 23 - Code for all major features in branch. Alpha test begun. Daily bug triage begun. Something similar to Steam milestone announced.
• January 30 - Beta test begun. Must fix bugs listed in Trac. Release notes started.
• February 9 - First Release Candidate built. Regression test defined. List of target activities to include in default image chosen. Something similar Water milestone announced.
• February 16 - Second release candidate chosen. Default activities tested. Something similar to Ice announced. Penultimate regression test set. Release notes new feature section, final edit. Open bugs section started.
• February 28 - Final release candidate chosen. Image sent to Quanta for factory verification. Final regression test done. Upgrade tests done for release notes.
• March 7 - Quanta ships first XO with new image. Final release notes written and reviewed. On time release!
• March 8 - Release announcement sent out.

First stab at schedule done by Gregorio 18:50, 2 December 2008 (UTC)

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::Deployability

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