Canonical Voices

Posts tagged with 'ubuntu'


Last week, at UDS, I was asked several questions about how Ubuntu Certification worked. I decided I would start a set of blog posts about several aspects of the certification programme, for people willing to know a bit more about how we test and what.

One of the most confusing bits about Ubuntu Certification are BIOS options. In several ocassions I was asked the questions whether UEFI (with and without Secure Boot) was going to be added as part of Ubuntu Certification or not.

The answer is both yes and no. I will explain it a bit more in detail.

In Ubuntu Certification we don’t test BIOS options, nor we change them. We try to install Ubuntu with what it comes with the system from factory, and it needs to work up to a certification level using those options. That means that if it is using Legacy BIOS, we will be testing Legacy BIOS, if it comes with UEFI without Secure Boot, that is what we will be testing. If it comes with Secure Boot enabled, Ubuntu will need to install out of the box with the keys already in that system.

From 12.10 we have started to parse the BIOS information as part of the testing process:

We will be updating the public certification site to show that information there as well.

Same thing for BIOS options. We test with factory default options, and only those. The goal of doing this is that Ubuntu Certified systems should provide and out-of-the-box Ubuntu experience. In some cases, tweaking BIOS options can improve the situation for non working systems, but that is something we don’t want to acept for Ubuntu Certification.


Read more

As weeks go by, we are getting closer and closer to Ubuntu 11.10 release and, therefore, to Ubuntu Friendly beta release.

First of all, the website is taking shape nicely and you can already see (and use!) an alpha version of the final site.

As you can see from the screenshot, right now all systems have only 1 star. This is the minimum rate a system can get (we give 1 start because, at least, it was able to install Ubuntu on it and submit results). The reason for all the submissions so far to have only 1 star is that a bug in Checkbox was preventing for one test considered to be “core” to run properly.

Call for Testing

The mentioned bug in Checkbox is fixed in our PPA and it is now ready to be used in Oneiric. If you run Oneiric it will be really helpful if you could install Checkbox from our PPA and run the full Ubuntu Friendly suite (this is the suite that runs by default).

  • Add our PPA to your software sources
  • Install the latest version of checkbox
  • Run “System Testing” on your system and submit to Launchpad

This will help us on two sides:

  • First, you will run the latest code in trunk. We are planning to release version 0.12.8 to Oneiric in a week, so this is the last time to fix critical issues. Should you find any issues during your testing, please, file a bug against Checkbox project.
  • On the server side of things, having a lot of data will help us testing the website to make sure it works fine when 11.10 gets released. Should you find any issues on the website, please, file a bug against the Ubuntu Friendly project.

Thanks for the help and I hope you are as excited as I am about the project!

Read more

Now we have a proper “How-to participate in Ubuntu Friendly” including a screencast on how to submit your system. We are just waiting to have a nice domain and Ubuntu 11.10 released to launch officially Ubuntu Friendly Beta!

Read more

Wednesday came and went! I will summarize our progresses as usual.

Ubuntu Friendly website

The website is coming together very nicely. Marc, who is working on the backend, worked closely with Mike, who is working on the frontend and they were able to communicate both, send a submission and show that information on the website. The website frontend still needs some polishing, but the basics are already there and working. One of the goals of the sprint was to have a full working solution, although not feature complete. I think we are going to make it.

Apart from this real progress we also worked a bit on new wireframes. Yesterday we got a comment on a previous post about having a mobile version of the site, as people will use their phones while shopping for a new system, to check how well they are reported to work with Ubuntu. We thought that it was a very good point, so we worked on some wireframes for the mobile version of the site:

Of course, we will focus on the desktop version first. But we will try to develop a mobile version based on these mock ups after that.


On the checkbox side we are almost done for what we expect to land in Oneiric. There is just one thing left: we are about to measure how long it takes to run the full suite for Ubuntu Friendly and we will remove the less useful tests to try to cut the running time to around 15 minutes.

Once we finish with that we will upload the new version to the archive.

Read more

Yesterday was a great day in the UF sprint and we got a lot of stuff done. I will summarize the interesting bits.

Ubuntu Friendly Website

As I said on the previous post, we still needed a way to visualize what components are working and which are not (to a certain level). To achieve that we have created a new “details” page, once you click on “more” on the configuration page.

That page will give you two pieces of information. First, it will show the complete list of components that were reported for that configuration:

On that list you will see the core components on the top (the ones we use to distinguish a configuration from another one) and a list of the rest of components found in all the units that were reported.

The second piece of information are the results that were reported per component:

On this view you will see the number of people that reported that a particular component was working and a percentage. We will have some colour code for the percentage, to have a quick visual view of it.

The “Related Bugs” tab is just a way of saying that this view could be extended in the future, but currently this is out of the scope for this release.


On the client side we also made some important progress. We finished mapping tests to components, so we can know which components are failing and which ones are passing.

We just merged our changes into checkbox trunk and we hope to have it uploaded to Oneiric early next week.

Read more

There seems to be a little bit of confusion about what the Ubuntu Friendly programme is and what it is not. People tend to think that Ubuntu Friendly is a certification programme and, because of this, they obviously don’t understand the idea behind core and extra components.

Let’s try to clarify things a bit with a small FAQ:

Is Ubuntu Friendly a certification programme?

No. Ubuntu Friendly is not a certification programme. UF is a community driven hardware validation programme. Its goal is to have a list of systems that people have tested with a particular release of Ubuntu and an associated rating, based on the results of their testing.

Let’s say is the next generation HardwareSupport wiki pages (, but with a better structure, as the tests will be written upfront, and the process to get a rating for a system will be the same for every system.

What does it mean that a system is Ubuntu Friendly?

Nothing, as there is not such concept. Ubuntu Friendly is just the name of the programme and yes, it was chosen because of the concept of a system being Ubuntu friendly (working fine with Ubuntu), but there won’t be a classification of systems that gained the Ubuntu Friendly status or not.

Instead of that, any system tested with the testing tools that we provide will make it to the Ubuntu Friendly list, with a rating associated with it. The rating will be between 0 and 5, that will give the user of the Ubuntu Friendly list an overview of how well a system works with Ubuntu and how many people have tested it.

Will this substitute the Ubuntu Certification Programme?

No. Ubuntu Friendly is not a certification programme and it won’t substitute the current Ubuntu Certification Programme. The UCP is a commercial certification programme, run by Canonical, and it will be still available for commercial partners. Opposite to the Ubuntu Friendly programme, the UCP is a go/no-go decision. A system is certified with Ubuntu or it is not, there are no ratings. To be certified with Ubuntu the system must pass all the tests specified in the UCP coverage list.

Read more

Yesterday we had our first meeting to start nailing down the Ubuntu Friendly programme. It was a great meeting, with lots of participation from both Canonical and non Canonical people.

Meeting logs and summary are available at the wiki.

One of the things that was agreed was the final separation of core and extra components.  The final list looks like (the tick represents a core component):

This list is the final list for Ubuntu 11.10 and was mainly based on a survey we conducted within the Ubuntu Friendly community.

We will improve coverage and might modify core components for future releases based on the feedback we get in the first Ubuntu Friendly release.

Read more

Why we need artists

Picture by theodevil

The Free Software community is a great community, but a bit narrow. Most of the people are geeks and there are many more men than women. Disclaimer: I would consider myself a geek. It is true that the older I get the less geek I am, but during my childhood, my early youth and my University years I was a true geek. And that was almost yesterday…

Artists is a very influential collective, they are one of the best PR any product can get. They influence people, the media and even governments. We need writers writing novels using Ubuntu, musicians making music using Ubuntu and video artists editing their films using Ubuntu.

Designers are also influential. Let’s face it, blogs by designers talk about more beautiful stuff that those of hackers. If you read Planet Ubuntu, a lot of the information there comes in the form of code. On a designer blog you’d rarely see the word branch if they are not talking about trees. Why Ruby on Rails got so much attention? Was because it was the best piece of free software ever? Probably not, but it attracted designers. Designers and developers starting working together using the same tools and they spread the word.

One of the examples I always use for the FLOSS community being too geek is PyRoom. PyRoom is a simple but great distractions-free writing application that, obviously, is coded in Python. I love the application and use it almost on a daily basis, but using the name of the programming language as part of your application is a clear indication that the technology you’re using is as important as the features your coding with it.

I am not saying that we need less geeks in our community, I am just saying that if we want to reach the 200M users goal, we need to have a wider community. And that’s why I backed Novacut on their Kickstarter project. Because they are focusing in talking to film makers as part of their design process. Because they have one in the team. Because I think they could help Ubuntu getting a wider and very much needed community. And they can fail, as anyone can fail, but I think it is worth supporting those brave enough to try. I am looking forward to seeing what Novacut brings.

As a side benefit I think that having a less geeky community will bring more women into free software. I’ve always defended that one of the reasons of the low ratio of women to men in FLOSS communities was mainly due to the geekyness of these communities. For social reasons (or a combination of social and biological ones), the proportion between men and women among geeks is far from the fifty percent. I am not trying to explain why: I am not a sociologist, nor a psychologist, but I think most people would agree that that’s the case. Bring more non-geeks to Ubuntu and women will be among them.

Read more

Last week, and thanks to the efforts of Brendan (among others), a lot of tests that used to be private were moved to Checkbox, the tool that we are going to use to test Ubuntu for the Ubuntu Friendly project, and are now public.

This means that a lot of new strings are ready to be translated:

We want Ubuntu Friendly to be as open as possible and that involves having the tests translated to as many languages as possible. We are aiming to collect as many results as possible, so allowing people who don’t speak English to test their systems and provide results is a very desirable feature.

If you speak a non-English language (or want tests to be in perfect Queen’s English), come to our translations page and submit your translation suggestions. Thanks!

Read more

Picture by madame_furie

One of the decisions that we took when defining the Ubuntu Friendly process was that we would distinguish between a core component and an extra component. A submission received with a failing core component would get a rating of zero (who wants to buy a bike with broken pedals?), and a submission with all its core components working would get a rating of 3 out of 5. The extra 2 points will be gained with working extra components.

But the question is, which components of a system should be considered core components?

This is a tricky question, as it will depend a lot of the uses a person gives to a system. But, in the end, we all have to take decisions, so we can make things happen. Obviously, core components in desktops won’t be the same ones as in laptops/netbooks, as their uses are completely different.

We have also to take into account that a system with all its core components will only get a 3 out of 5 from those core components, so it is totally OK to leave outside of the core components an important one, as it will only mean that if it fails, the system won’t get a 5 out of 5. For example, for a laptop I would consider wireless a core component. I just can’t imagine using a laptop (if it comes with a wireless card) if the wireless network is not working. But I can imagine using  a laptop where the wired ethernet card is not working. I would consider the wired network an extra component for a laptop. Obviously, the perfect laptop will have both working, that’s why we would need both working to be able to reach a rating of 5 out of 5.

So, what are your ideas? What components are vital for your laptop/netbook? What components in your desktop you couldn’t live without? Comments welcome!

Read more

Picture by stefanvds

Last week, current members of the Ubuntu Friendly Control gather together and we took the opportunity to discuss some of the Ubuntu Friendly processes. One of the biggest questions that we wanted to answer was what it meant for a system to be Ubuntu Friendly. How and where should we draw the line between an Ubuntu Friendly system and the rest of systems. After a very good discussion and brainstorming we came up with a different solution: we wouldn’t draw that line.

The basic idea from where we will define the way a system is tested and have an Ubuntu Friendly rating is the division between core components and extra components. What is a core component or an extra component we care about will be decided later in the process.


Ubuntu Friendly tests will be grouped by the component that they test. In order for a submission to be consider valid and accepted in our rating system, all the tests that cover the core components should have been tested (either pass or fail, but tested).

If a submission does not contain results for ALL tests that cover, the system will reject that submission and it won’t count for Ubuntu Friendly status.

Once that the core components have been covered, the submission will be accepted.


Rating per submission

The rating for a particular accepted submission (at least all tests for core components) will be determined by the number of components that passed or failed. The rating will be between 0 and 5.

If any of the tests that cover the core components failed, the submission will get a value of 0. Even if any of the extra components worked.

If the all the tests that cover the core components passed, the submission gets a rating of 3.

The two remaining points to get to a rating of 5 are covered by the extra components with a simple rule of three. If a system does not have any extra components, and, again, all tests covering core components passed, the submission will receive a rating of 5.


We have a list of 10 core components (UFC) and 7 extra components (UFE) that we care about. Any other component we will list it as additional component (AC).

System Components Pass Results Rating
Laptop1 6UFC, 3UFE, 0AC 5/6 UFC, 3/3 UFE 0
Laptop2 10UFC, 4UFE, 3AC 10/10 UFC, 1/4 UFE 3.5
Desktop1 7UFC, 5UFE, 1AC 7/7 UFC, 5/5 UFE 5
Netbook1 4UFC, 1UFE, 0AC 4/4 UFC, 0/1 UFE 3

Global rating per system

The global rating for a particular system will be the average of all the submission for that particular system.

Ubuntu Friendly Website

Each release of Ubuntu will get its own list. By default, the list shown will be for the latest release of Ubuntu.

Systems will be ordered by global rating first, and number of submission after.

Systems with very bad rating will also appear in the list. There will be no boarder line to call a system Friendly or not, it will be just a rating systems


Ubuntu 11.04 Friendly

Latitude 2120             4.3   (30 submissions)
Vostro                    4.3   (13 submissions)
Acer EeePC                3.2   (40 submissions)
Mac Book Pro              2.9   (3  submissions)
WinPro Laptop             0.3   (50 submissions)


The representation of the ratings will be graphical (stars, bars, etc). Clicking on any of the results will give us the details of each of the submissions.

People will be able to filter by model, type of system, minimum rating, etc.

Giving Feedback on Results

Any user will be able to give feedback and comments for a particular system without needing to run the tests. The feedback will be things like “bluetooth is supposed to be working, but it is not working for me”. These comments will be showed on the details of a particular system, but they won’t affect the actual rating of the system.

Waiting on your comments!

As in previous processes and thoughts about Ubuntu Friendly, we are looking to get as much feedback as possible, and this part of Ubuntu Friendly is no different. Please, join us in the Ubuntu Friendly Squad and have your say!

Read more

As you might already know, we will do some changes to Ubuntu Certification in the Oneiric Release. Victor Palau has written a nice summary of some of those changes:

[...] we are planning to close down the “Ubuntu Ready” programme in time for Oneiric Final Release.

The aim is to simplify the public Canonical endorsed certification programme to only one:“Ubuntu Certified“.

To straighten out any confusion about what our certification offering will be here is a quick fact sheet about certification:

Existing Ubuntu Ready Certificates
We will not be offering new “Ubuntu Ready” services to OEM/ODMs. The existing Ubuntu Ready certificates will be maintained on the public website until the applicable releases reach end of life.

Remote Testing
We will continue to offer testing tools to partners and the community.The objective is for a common test tool for partners and community will be available within the Ubuntu ISO (from Oneiric).

Ubuntu Certified for Clients
Ubuntu Certified will continue to require hardware to be submitted to Canonical for testing. Ubuntu fortnightly Stable Release Updates means that certified systems are required to be tested every 2 weeks to ensure no regressions are introduced.
Remote testing can be used by partners as a way to assess if certification will be successful before engaging in a contract with Canonical.

Ubuntu Certified for Servers
While Certification of single servers follows the same process than client certification, we are concentrating our efforts on Certifying full server lines from OEMs.
In order to achieve this objective, the full server line is analysed by the appropriate TAM, a component matrix is produced and small representative set of servers is provided to Canonical by the OEM to test in-house, while the rest of servers are test remotely.

Ubuntu Certified (Pre-install Only)
A OEM or ODM shipping a pre-install custom ISO with their systems can apply for Ubuntu Certified (Pre-install Only).

Ubuntu Friendly
Ubuntu Friendly in not a Canonical certification programme. Ubuntu Friendly is a Ubuntu community hardware validation programme that recognises the need for community and partners to list various degrees of working Ubuntu hardware publicly. At the same time, we expect this initiative to increase the visibility of which hardware components work with Ubuntu.
Participation in Ubuntu Friendly is free, done in the open and will utilise the remote testing tools provide by Platform Services.


Read more

Picture by Javier Mcallan

One of the things that we will need to discuss and decide to run the Ubuntu Friendly programme is what makes a particular system Ubuntu Friendly. Obviously, one of the ways to do this is to make the Ubuntu Friendly Control review the submissions that are considered complete and correct and determine whether those results are enough to consider the system Ubuntu Friendly.

This, obviously, scale badly if the number of submissions grow to a number that make the revisions of submissions the bottleneck of the programme.

The other option, that I think we should explore is create a way to auto regulate results, partly manually and partly automatically. Think On that site, people asking questions can accept or reject answers from people, answers can be voted up or down, etc. The same way, I foresee an Ubuntu Friendly site where people from the Ubuntu Friendly Squad could:

  • Reject results that are incomplete or invalid
  • Vote up results that are complete
  • Ask for more information to the tester, if some discrepancies are found
  • etc.

With this information, an algorithm could then decide whether a particular system is Ubuntu Friendly or not. The details of that decision would always be public. For example:

Thinkpad 420s is Ubuntu Friendly.
Details: 5 positive results (3 voted up), 1 negative result (1 voted down, 1 incomplete).

Of course, at any point, members of the Ubuntu Friendly Control could override the algorithm decision, and remove a system from the list of Ubuntu Friendly if necessary.

Read more
Ara Pulido

On First Experiences

Everybody agrees how important the Out-Of-Box experience is for a product. If the users’ first experience with any kind of product is frustrating it is very likely that they’ll return it and never look back.

On Operating Systems, usually, this first experience is turning on the computer and reply to some basic questions. For all the major OS like Windows or Mac OS, the software comes preinstalled in the computer. For many users, therefore, that’s the computer itself: something that you turn on and it starts working.

For Linux is quite different. Despite the efforts that some companies (including Canonical) are doing in order to be easier and easier to buy a computer with a Linux distribution preinstalled, nowadays, the first experience a user has with Linux is, most of the times, a CD and an installation process. Well, if you then want to have one of the best first Linux experiences ever, wait until Sunday and install the brand new Ubuntu 10.10. Its installation process is, ladies and gentlemen, pure joy:

I would like to congratulate the Ubiquity team for the fantastic work they do every six months. They make the first experience of those people who start with Linux better every time. It is great to have the opportunity to work with you, guys.

Read more
Ara Pulido

As you might know, Ubuntu version for netbooks, UNE, is having a major re-engineering work for Maverick Meerkat,  soon to be Ubuntu 10.10. The old interface, which included packages like netbook-launcher or maximus, is going to be replaced by Unity. If you don’t know what Unity is, the nice people behing OMGubuntu published some days ago a nice review of the brand new UNE interface.

I will give you a clue: it does look very different from what you’re used to. That’s why we want to collect as many reports as possible of people upgrading from UNE 10.04 to 10.10 (with Unity).

My experience upgrading

OK, I don’t want to ask people to test something if I haven’t (and I have the means for it). I took my Dell Mini 9 (well, technically is Canonical’s, but, anyway) and I installed Ubuntu Netbook Edition 10.04.1 in Spanish. The installation went very well and fast.

After reboot, I updated my 10.04 installation and started the upgrade to Unity. Although the upgrade itself did not have any major problems it took almost six hours! Of course, I reported this as bug 646638. I talked with Michael Vogt on IRC and he will investigate.

Once the upgrade finished everything worked as expected: the language was still Spanish and there were no major crashes. Nevertheless, the global menu stayed there with “File Editar” even when no applications were running. I filed that as bug 646890 in Unity.

Apart from that, I found a couple of bugs in the Dash, but unrelated with the upgrade itself. These are bugs 646758 and 646756.

Your experiences upgrading

My system is not a real system. I use the Dell Mini 9 with SSD 8GB for testing purposes. I don’t use it on a daily basis. I reinstall almost every flavour of Ubuntu on it every milestone. My upgrade experience was from a nice, cleaned, UNE 10.04 to 10.10. No PPAs or third party software installed.

That’s why we need real feedback from the people that often use UNE 10.04 on their upgrades to 10.10. If you want to participate in our testing effort, just follow the next steps:

  1. Create an account in our tracker
  2. Upgrade to Maverick
  3. Report back!

Use my testing report as an example. You see that you can add comments (like the system you used,or general impressions) and, of course, add bug numbers if you encounter any.

Thanks and happy testing!

Read more
Ara Pulido


Firefox 3.0 and xulrunner 1.9 are now unsupported by Mozilla. Rather than backporting security fixes to these now, we are moving to a support model where we will be introducing major new upstream versions in stable releases. The reason for this is the support periods from Mozilla are gradually becoming shorter, and it will be more and more difficult for us to maintain our current support model in the future.

What we are going to do

We are going to release Firefox 3.6.4 as a minor update to the 3.6 series in Lucid. This will also be rolled out to Hardy, Jaunty and Karmic (along with xulrunner The update for Lucid is quite trivial, but the update in Hardy, Jaunty and Karmic is not quite as simple.

Before releasing these updates to the public, we need testing in Firefox, the extensions in the archive and distributions upgrades after those updates. We have published all these packages in a PPA and we will track test results before moving anything to the archive.

How you can help

We need people running *Hardy* (Jaunty and Karmic will see a similar call for testing in the following days) in bare metal or a virtual machine. If you are willing to help, you can follow the instructions below:

  1. Add the Mozilla Security PPA to your software sources

    You need to manually edit your /etc/apt/sources.list and add the following lines:

    deb hardy main
    deb-src hardy main

    After saving the file, you have to run:

    sudo apt-key adv --keyserver --recv-keys 7EBC211F
    sudo apt-get update
    sudo apt-get dist-upgrade

  2. You have to have an account in our tracking system. Go to and click on “Log In” and “Create New Account”
  3. Explore your Firefox installation

    Basically we want people to perform the same activities that the do daily, without issues. In order to make testing easier, this is a checklist of things worth looking:

    • The upgrade to Firefox 3.6.4 goes smoothly.
    • The extensions get upgraded as well.
    • All the Firefox plugins (i.e. Flash, Java) still work.
    • The extensions work correctly.
    • Full distributions upgrades are not broken.
    • Upgrades work with only the security pocket enabled (ie, hardy-updates disabled)

To report your findings you need to use the test tracker.

Once you have selected the Hardy image, you will see a set of “testcases”, with a summary of how many reports have been sent. Obviously, the most important one is “Firefox”.

List of testcases

Once you open one of the testcases, you will be able to report back your findings if something went wrong. Even if everything went fine, it is always good to report back the success (“Passed”) with a comment on the activities you performed.

Report back

Use the “Firefox” testcase for general testing (upgrade, rendering, plugins, etc.) and the rest of the testcases if you want to report something more specific (Upgrades to Lucid, specific extensions errors, etc.)

IMPORTANT!! How to file bugs

As we are testing a PPA, not an official Ubuntu package, if you find an issue is NOT OK to file a bug in Launchpad. Rather than doing so, please, just explain your issue in the Comments field of the tracker and mark the test as Failed.

The tracker requires a bug number in order to mark a test as Failed. To bypass this requirement, just use the bug number “1″ ;-)

Thanks for helping to maintain secured Ubuntu stable releases!

Read more
Ara Pulido

I have been busy with the release of Ubuntu 10.04 LTS and, although it may seem that Mago activity has decreased, there are some news related to the project that I want to share before UDS.

Ubuntu 10.04 LTS has been released with Mago 0.2, which is the release of Mago compatible with LDTP 2.0. Earlier this year, LDTP team released a complete rewrite of the testing framework in Python. After LDTP 2.0. arrived in Lucid, Mago suffered some weeks of instability, until it was working again with the new API. Also, I gained upload rights for ldtp and mago packages last week and, hopefully, this will be reflected in more activity during the Maverick cycle.

There is going to be work related to GUI testing during Maverick cycle, and some of them have been already reflected as blueprints for discussion during UDS:

Mago internationalization:
Mago works only with “C” locale applications. We need to modify it in order to make it work with different locales. This will be useful for local Ubuntu derivatives and to test language packs.

Mago Daily:
We aim to be running Mago tests on a daily basis. One of the biggest challenges to achieve this is having perfect integration of Mago with Checkbox. We will be discussing previous problems and will try to find a solution.

Roundtable: GUI Testing:
We will be discussing the different solutions for GUI testing available, their advantages and disadvantages. Sikuli, Mago, kvm-autotest, among others.

So, if you are coming to UDS (or want to participate remotely) and are interested in automated GUI testing, feel free to subscribe to those blueprints and participate in the discussion. See you all there!

James Tatum, a Mago contributor who is also coming to UDS, points me to another blueprint for discussion.

Simplify the creation of tests in Mago:
Adding applications to the Mago library is cumbersome. To foster the creation of more test cases, we will discuss ways to make this easier.

Read more
Ara Pulido

Ubuntu Global Jam
As many of you already know, this weekend we are celebrating the Ubuntu Global Jam, an event where all the participating LoCo teams gather together and contribute to make Ubuntu even better. There are lots of ways to contribute, from developing, to translations, documentation, packaging or testing. This time we have introduced a new and very valuable way to contribute: Upgrade Jams.

The objective of the jam is easy and everybody can participate prior to start contributing to the rest of the tasks: upgrading your own machines to Lucid Lynx Beta 1 and report back your experience. You can find information about how to run an Upgrade Jam in the wiki.

Remember! When arriving to your local Ubuntu Global Jam, and before starting contributing to the rest of the activities, upgrade your system to Lucid! The ISO tracker is already waiting for your results!

Read more
Ara Pulido

If you have ever participated in Ubuntu ISO testing you may know what this title is about. To coordinate testing and to avoid duplicating efforts, every time one of us starts a new testcase, we enter a line like the one in the title in the #ubuntu-testing Freenode IRC channel.

In this example it means that I have started the Full Disk testcase for the Ubuntu Live CD i386 image. Others willing to help will know that I am already working on that one and will be able to concentrate their efforts in other testcases.

This system is far from perfect, as not everybody is in IRC and, even if you are, you can lose the messages sent before you logged in.

To improve the system I have added a new “Started” status to the test reports. Now, when you start a testcase, instead of having to communicate it in the IRC channel, add a “Started” result to that testcase and others will know that you are working on it (it will show up in the list of results with an icon of a clock.

Testcase started

Hopefully this will improve the coordination of the ISO testing activities.

Read more
Ara Pulido

As you may already know, next Ubuntu release, Lucid Lynx (10.04) is an LTS release.

For testers this means one important thing: upgrades should be smooth from either Ubuntu 9.10 (Karmic Koala) or latest Ubuntu LTS release (8.04, Hardy Heron).

As we all know, nowadays, computer storage is very very cheap, but bandwidth is not. Later in the cycle we are going to need to test as many upgrades from Hardy and Karmic as possible. So, why not planning ahead and start downloading today Hardy and Karmic images? The unstoppable Shane Fagan has started doing so already! You rock!

Later in the cycle you will be able to easily install Hardy or Karmic in a spare machine or a virtual machine and upgrade from there. You will have part of the work done. And you can start contributing to your beloved distribution just now :-)

Other releases from Ubuntu derivatives can be found at:

Read more