• Intro
• Downloads
• Community
• Development
• News
• TALK

Community SSU

Testing

Stable

What is it?

Seamless Software Update (SSU), is the term Nokia used to brand the over-the-air updates of Maemo.

Community Seamless Software Update (CSSU) is being developed by the Maemo community, for the Maemo community. It aims to deliver fixes which can't be delivered easily through Extras, such as core Maemo packages. It won't, however, bundle software which can be installed through the Extras repositories.

There are two such efforts for the Maemo platform. This page describes the one for Fremantle (Maemo 5, as used in the Nokia N900). The Diablo Community Project is doing the same for Diablo (Maemo 4, as used in the Nokia N800 and N8x0).

Who is it for?

Long-term: all N900 users/owners.

For now: power-users, developers, Nokia/Maemo/MeeGo engineers, testers, documentation writers and those willing to risk a re-flash in order to help.

Installation

1. Make sure you're running PR1.3, Nokia's last official Maemo 5 update. To see if you have PR1.3, go into Settings > About product, you should see under Version it has the numbers beginning with 20.2010.36.
2. Click on the Install testing button above. (use http://j.mp/communityssu as a quick link to this page from your Nokia N900)
3. Hildon Application Manager (HAM) will launch and appear to be doing nothing but after a second or three it will display the first installation, so be patient. In all, there are a series of installations for which HAM will prompt you with messages and warnings. Click "accept" and "done" for each and let HAM install all the community packages.
4. Once done (ie. no further install prompts appear after some while), close HAM and go into the applications menu. Look for Community SSU and launch it. This will then automatically run through a series of scripts to ensure HAM will now be using community repository for updates.
5. HAM will re-open and present a system upgrade called Maemo 5 Community SSU. Once installed, your device will reboot.

Problems? Check the Installation FAQ

Contributing

Can you write documentation? If so, it'd be great to flesh out the wiki page with installation instructions (to make it easy for users to install without worrying about missing a step or getting it wrong); explain more about the SSU and generally spruce up the wiki page and maintain things like the changelogs etc.

Were you involved in developing Maemo? If so, with Nokia now looking to Harmattan and MeeGo, we'd love to see your itches addressed in the Community SSU (CSSU). Have you always wanted to implement something in hildon-desktop, but Management stood in your way? We'd love to have it!

Have you written a patch for Maemo? Raise a bug and let's get it in the CSSU.

Are you a developer? There are numerous patches floating around for hildon-desktop; but they can't be included in the CSSU until they are configurable (via gconf) and default to off.

Want to test? Not only testing this release, but writing test scripts so that each release of the CSSU can get sanity checked before unleashing it into a "stable" repo for end-users. How do we do it? What should be tested? How is it organised?

Want to organise? There's still lots of process left to organise; hopefully there'll be bugs and features to triage and manage in bugs.maemo.org as well as communication of the testing, releases and end-user readiness of the CSSU.

For more information: contact MohammadAG on #maemo-ssu on FreeNode IRC or council@maemo.org.

Changelog

Changes in the SSU between PR1.3 and various SSU releases.

QA and bugs

Quality is of paramount importance to the Community SSU. There are, therefore, two repositories: testing and stable. Changes are carefully tested, with an extensive set of tests, before things are made "stable".

If you have found a bug, in either the testing or stable releases, please raise a bug. Getting involved through testing, bug triaging and running of the tests is a good way to get involved; as, of course, is writing documentation!

Development

The Community SSU is developed and managed through Gitorious. Bugs are tracked in Bugzilla. Collaboration largely happens on IRC. Getting involved through development, bug triaging and managing developers is a good way to get involved.

What´s to come

While everything is organised and getting geared up, the first goal is to test that the Community SSU enabler and it's packages are stable enough to release to the general public. Above you will find a link to Bugzilla with bugs tracked since this release but when things are running smoothly, older bugs will be addressed too. Also, improvements are on their way, such as these. You can read more about them and others, and how to enable them here.