12.1.0
12.1.0 an in-development OLPC OS release, focusing on shifting parts of the Sugar UI to the GTK+ 3 toolkit and to new system technologies present in Fedora 17. The target platforms are Target platforms::XO-1, Target platforms::XO-1.5 (including XO-1.5 High School Edition) and Target platforms::XO-1.75.
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-07-02
Release notes: Release notes/12.1.0
Download and installation
Development builds are available here:
New builds are announced on the devel mailing list.
XO-1.75 and XO-1.5
To install from Open Firmware on an unlocked XO-1.5 or XO-1.75, download a .zd file to a USB drive. Choose the correct one: there are several. Files which end in .zd2 are for 2GB media and .zd4 is for 4GB media.
Insert the USB drive into the XO-1.5, get to the Ok prompt and type:
fs-update u:\osXX.zdN
Where osXX.zdN is the file you downloaded, for example os22.zd4.
XO-1
To install from Open Firmware on an unlocked XO-1, download the .onu and .uim files to a USB drive.
Insert the USB drive into the XO-1, get to the Ok prompt and type:
update-nand u:\osXX.onu
where osXX.onu is the .onu file you downloaded, for example os22.onu.
(Watch out, there's a trap. Never use copy-nand for this file format. copy-nand was for previous releases with .img and .crc files, but we no longer use it for .onu and .uim files. copy-nand might seem to finish okay, but your XO-1 won't start. If that happens, do it again using update-nand as above.)
Developers
The release is built with Build system::OS Builder version Build system version::5.0.x (master) under Build platform::Fedora 17, using f17-xo1.ini, f17-xo1.5.ini and f17-xo1.75.ini at this point in the development process. The f17, f17-xo1, f17-xo1.5 and f17-xo1.75 RPM dropboxes are used.
Fedora package inclusion process
(draft)
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, the only required step is step 1. 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 we can lump it into batches.
The entire process is elongated by the fact that pushes into x86 updates-testing are fast (daily), but updates-testing is currently not built for ARM; ARM packages only get built when things get pushed to stable. In the process below, we scratch-build the ARM packages when ready, and keep them in public_rpms until the ARM build system later comes along and builds them officially.
- Produce source tarball, upload to relevant place.
- 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
- Submit an update for F17.
- fedpkg update
- Scratch-build your package on ARM.
- arm-koji build --scratch f17 $(fedpkg giturl)
- When the ARM scratch-build completes, download the RPMs and put them in your public_rpms/f17. Your packages are now ready for build inclusion.
- When bodhi emails you saying that your F17 update can be pushed to stable, push it.
- When the ARM koji builds your updated package for F17, delete it from your public_rpms. This tends to happen very soon after bodhi pushes your package into the F17 stable repository (bodhi emails you about this).
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 12.1.0, your bug report will then be triaged into the appropriate place.