8.2.0

8.2.0 is a future release in development and early testing (as of July 2008).

Release Notes

Please contribute to the 8.2.0 Release Notes.

Terminology

blocker

We can agree on a minimal set of bugs which are so nasty that we know in advance that we could never deploy an OS containing them. These bugs are called 'blockers'. We will not ship 8.2.0 with open blockers.

polish

We can agree on a more inclusive set of low-risk 'polish' bugs that we should attempt to resolve as time and resources permit.

milestones

Our ideal 8.2.0 release procedure will consist of motion toward the delivery of three milestone builds:

• an Alpha image with few blockers,
• a signed Beta image with some polish, and
• a signed Final image with no blockers and, we hope, some polish.

Schedule

Preparations for the 8.2.0 release began in December, 2007 and rapidly expanded in March, 2008 when, having completed the 8.1.0 release, the Sugar team began working toward the goal of shipping their UI redesign. In March, it was decided to try to ship the release in August on the basis that this was the earliest time at which integration of a useful body of features could be completed. The current schedule calls for the completion of the 8.2.0 release in mid-September as follows:

8/27: we will nominate a build as our Alpha image for maximal testing. If miracles occur, it will have no blockers. :)

9/03: change control tightens (i.e. "we freeze").

9/05: we will officially refresh translations.

9/07: we will conduct a preliminary security audit of the OFW, EC, kernel, and initramfs changes relevant to initial activation security.

9/10: we will publish a signed Beta reference OS and G1G1 derivative images.

9/17: we will publish the signed Final images of the 8.2.0 reference OS, release notes, and the G1G1 derivative image.

Priorities

1. PLEASE RESOLVE BLOCKERS.
   • Report of 8.2.0 blockers.
   • Even if they aren't assigned to you, please help!!!
2. OTHERWISE, help out with the TESTING effort
   • Systematic testing
   • Friends in testing
3. OTHERWISE, help out with the DAILY TRIAGE of new bugs
   • http://tinyurl.com/5zj4cs
   • Report of bugs proposed as 8.2.0 blockers
   • 1500 UTC on #olpc-meeting
4. OTHERWISE, UNTIL 9/03, you can POLISH
   • Report of 'polish:8.2.0' bugs
   • subject to 'light change control'; see below

Development stream

We have a pilgrim stream named "8.2" which is where release candidates will be developed.

• Stream
• ChangeLog
• Differences vs joyride

Builds are manually triggered by C. Scott Ananian.

If developers wish to get packages/updates included in the stream, they must first be committed to joyride. After successful testing in joyride, file an inclusion request on the corresponding trac ticket. Approval will come from release engineering before the package is included in the stream.

Useful links:
Currently useful links

http://dev.laptop.org/~bert/8.2-joyride.html
- Bert, could you please make a version of your status pages which shows package changelog entries? Thanks in advance!

http://dev.laptop.org/report/21
Fixed-timespan report on changes to 8.2.0 bugs.

http://dev.laptop.org/report/20?TIME=400000;page=1;
Adjustable-timespan report on changes to 8.2.0 bugs.

http://pilgrim.laptop.org/~pilgrim/xo-1/streams/8.2/
8.2.0 build stream

http://xs-dev.laptop.org/~cscott/xo-1/streams/joyride/
Joyride build stream

From http://lists.laptop.org/pipermail/devel/2008-July/016457.html

Feature Set

XO Base Features - Base features of the XO up to release 8.1.1.

New Features listed in the 8.2.0 Release Notes. The Release Notes are under construction and subject to change
See Release_Notes/8.2.0

Release Contracts (definitions) Use Keyword definitions below to interpret status of Release Contracts

Current List of Must Fix Bugs These are marked by blocks:8.2.0 in the keyword field. They may be triaged down later as needed but for now they are flagged as must fix.

This Trac query list major feature sets. Each item should contain all the relevant tickets for that feature set.

Keyword definitions

1. 8.2.0- means not likely to make the release based on current status
2. 8.2.0? means may make the release based on current status
3. 8.2.0+ means likely to make the release based on current status

Definition of 'Builds' to deliver in 8.2:

1. Base OS
2. Image with Base OS + G1G1 Activities
3. Image with Base OS + Peru Activities

Documentation:

1. Release Notes
2. Better "Getting Started" doc
3. Any changes needed for the Deployment Guide

Requirements for Support in 8.2 (need testing, may not need development):

1. Upgrade to new release
2. Cleaninstall
3. Backward compatibility
   • Users' data will continue to load and be modifiable after upgrade (no change in activities)
   • Users' data will continue to load and be modifiable after upgrade of both OS and Activities

Notes and Early Comments Kept for Historical Purposes Only

Requests:
http://lists.laptop.org/pipermail/devel/2008-June/015203.html

Previous discussion of priorities:
Priorities-2008

Older priority discussion:
User:Mstone/Commentaries/Releases_1

Update on feature status:
http://lists.laptop.org/pipermail/devel/2008-June/015324.html

Laundry list of everything supported on XO. Not a list of new things only.
OLPC 8.2.0 Features

Possible target stream?
OLPC-3

Requests from Nepal via Bryan

1. Need to be able to launch activities such as Scratch, EToys, Pippy, etc. by clicking on a hyperlink in browse. The activity wouldn't run in the browser. We need this functionality in order to effectively use Moodle in our schools.

Here's the ticket I opened on the http://dev.laptop.org/ticket/6958

2. Need to be able to remove activities via the GUI, including installed activities, to make room for new ones. We are working on Offline Moodle activity bundles for courses. Each course will be subdivided into weekly modules. these modules will quickly fill up the ssd. kids will need a way to remove activities themselves to make room for new ones.

http://dev.laptop.org/ticket/7071

Possible Release Criteria Wish List

From: http://lists.laptop.org/pipermail/devel/2008-July/017172.html

See also ensuing thread for full discussion.

Start e-mail:

I'm willing to compromise where needed (e.g. boot time isn't that critical) so treat this as best case or starting position.

Two ways to slice this:
1 - Better than the last release (8.2.0 v 708, 703, and 656)
2 - Works as expected

For case 1, where it says "the same", read "same or better" or "same or more" as appropriate

For case 2 where it says "the same", read "as documented" or "as expected".

Stability Requirement for 8.2.0

1 - Start activities at the same speed (including but not limited to all fructose activities)
2 - Boot to home at the same speed.
3 - Cursor control the same, including number of XOs where it moves without input or moves without correlation to finger on touchpad
3 - Connect to the same APs in the same time and with the same user feedback. (e.g. blinks then shows white circle).
4 - Connect to active antennas in the same time and with the same user feedback (e.g. blinks then shows white circle).
5 - Run all the same activities (can require activity upgrade within documented bounds). Includes allowing activities to mesh the same way.
6 - Connect to mesh with the same number of XOs in the same time with the same failure rate.
7 - Save and open files for all activities. Fructose activities at a minimum otherwise all activities per 5 above. Including when journal has thousands of entries.
8 - Use the same NAND space.
9 - Always boots up, especially when there is no space on NAND
10 - Open and close all activities per 5 above.
11 - Must support all languages and keyboards previously supported. "support" means all previously translated strings still work in activities and sugar. All language types work the same (e.g. RTL)
12 - No new cases where the XO crashes and needs hard reboot.
13 - No new cases where the cursor stops responding (AKA hangs) for more than 30 seconds.
14 - Sound and video recording and playback must record at the same rate. Must playback all the same kinds of files. Must playback with the same quality (assuming all other variables constant, e.g. network, RAN=M, disk space, etc.)
15 - Browse must render the same web sites as before. See also http://dev.laptop.org/ticket/7421
16 - USB read, write, mount and unmount must work the same and for all the same devices.
17 - Mouse and keyboard must connect and work the same
18 - Journal has the same capabilities.
19 - Must use the same or less power for the same user interaction
20 - Must have the same security mechanisms and be as secure as previous releases.
21 - Must be installable in the factory and upgradeable from 656, 703 and 708 via USB or network.