13.1.0

13.1.0 is an in-development OLPC OS release, focusing on adding support for the XO-4 laptop and adding touch support to Sugar. The target platforms are Target platforms::XO-1, Target platforms::XO-1.5 (including XO-1.5 High School Edition), Target platforms::XO-1.75 and Target platforms::XO-4.

The release plan can be found at /Release plan.

Status

Status: Status::in development (see /Release plan and Release Process).

To be released on: Release date::2012-12-13

Release notes: Release notes::Release notes/13.1.0

Significant known issues

The bug tracker is http://dev.laptop.org under the milestone 13.1.0

Please only add items to the list when they have a corresponding ticket mentioned.

XO-4

• No screen rotation yet (<trac>12148</trac>)
• No sound yet #12155
• No suspend/resume yet #12147
• Sugar screenshots are all black (SL#4104)
• Firmware on A models can't be upgraded. Please contact OLPC if you have not received a B model as a replacement.
• The ambient light sensor is not supported yet (<trac>12243</trac>)

If running firmware Q7B01, the system will not boot (you just get the 'ok' prompt). You must upgrade manually to e.g. q7b02 at the ok prompt:

  ok flash u:\q7b02.rom

Once you are at Q7B02 or later, the automatic firmware upgrade comes into play.

Misc

• Modem dongle does not appear in frame (#12248)
• Alt-tab doesn't switch Activities (SL2405)
• Frame volume up/down stays at zero (<trac>12237</trac>)
• Menu does not dismiss when resuming Activity (SL#4129)

Download and installation

Development builds are available here:

• http://build.laptop.org/13.1.0

New builds are announced on the devel mailing list.

XO-1.75, XO-1.5 and XO-4

To install from Open Firmware on an unlocked XO-1.5 or XO-1.75, download a .zd file to a USB drive.

Insert the USB drive into the XO, get to the Ok prompt and type:

fs-update u:\X.zd

Where X.zd is the file you downloaded, for example 31001o1.zd (for XO-1.5), 31001o2.zd (for XO-1.75) or 31001o4.zd (for XO-4).

XO-1

To install from Open Firmware on an unlocked XO-1, download the .img and .crc files to a USB drive.

Insert the USB drive into the XO-1, get to the Ok prompt and type:

copy-nand u:\X.img

where X.img is the .img file you downloaded, for example 31001o0.img.

Online upgrade

For updating from a previous release to a 13.1.0 development build, or from one 13.1.0 development build to another, you can use olpc-update. For example, to update to build 1, run one of the commands below in the Terminal activity, depending which laptop model you are using:

sudo olpc-update 13.1.0d_xo4-1
sudo olpc-update 13.1.0d_xo1.75-1
sudo olpc-update 13.1.0d_xo1.5-1
sudo olpc-update 13.1.0d_xo1-1

Developers

The release is built with Build system::OS Builder version Build system version::6.0.x (master) under Build platform::Fedora 18, using f18-xo1.ini, f18-xo1.5.ini, f18-xo1.75.ini and f18-xo4.ini at this point in the development process. The f18, f18-xo1, f18-xo1.5, f18-xo1.75 and f18-xo4 RPM dropboxes are used.

Fedora package inclusion process

For contributions in the form of updated RPM packages that are part of Fedora, the process is a little complicated due to the fact we work with multiple architectures and ARM is not yet a primary Fedora architecture.

The entire process is explained below. However, only the first and last steps are required. Feel free to skip some or all of the remaining steps - just make sure you leave a note on an "add to build" ticket noting which steps you have done. Daniel and Peter are more than happy to take on the packaging work on your behalf, and they can lump it into batches.

1. Produce source tarball, upload to relevant place.
2. Commit spec file to Fedora git, push and build for x86
   • Commit your change on both the f17 and master branch. Suggestion: commit on F17 branch, then use git merge to fast-forward master to the same commit.
   • Ensure you are on the f17 branch.
   • fedpkg push
   • fedpkg build
3. Submit an update for F17.
   • fedpkg update
4. When bodhi emails you saying that your F17 update can be pushed to stable, push it.
5. Put the relevant trac ticket in "add to build" state, noting which of the above steps you have completed.

ARM is intentionally left out of the picture here. Your package will be built automatically on ARM after a day or so. (Sometimes the build manager will build it manually in order to avoid the wait).

Non-Fedora package inclusion process

For packages that are maintained outside of Fedora, the inclusion process is:

1. Build, test and publish the RPM (including source RPM) inside the relevant RPM dropbox.
2. Put the relevant trac ticket in "add to build" state with a request for inclusion

Activity inclusion process

At this time, the build system pulls the latest 0.98-compatible activity versions directly from http://activities.sugarlabs.org.

Bug reports

We are now looking for bug reports on all levels - system, Sugar, activities, ...

Sugar-specfic bugs and activity issues should be filed at http://bugs.sugarlabs.org. System-related bugs should be filed at http://dev.laptop.org. If in doubt, ask on the mailing list first, or file at OLPC and let us take care of it for you.

For OLPC tickets, leave the milestone field blank but mention clearly that you are testing 13.1.0, your bug report will then be triaged into the appropriate place.