Archive for June 2010
This week is a release week. On Thursday, the Release Team will be releasing Maverick Alpha 2, the second development release for this cycle. As every release week, this is going to be a busy one.
- I am syncing my ISO images to have them more or less prepared when the first candidate images start to appear. I am using dl-ubuntu-test-iso to sync my ISOs. If you want to use it as well, you just need to install the ubuntu-qa-tools package.
- I am going to prepare some VM machines with different flavours of Lucid on it, to test the upgrades to Maverick as soon as possible.
- I will spend most of the week testing the different images and reporting back my findings to the ISO tracker. If you want to help with ISO testing this week, make sure you read the documentation first.
- On Friday, once Maverick Alpha 2 is released, I will be upgrading my own machine to Maverick.
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 22.214.171.124). 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:
- 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 http://ppa.launchpad.net/ubuntu-mozilla-security/ppa/ubuntu hardy main
deb-src http://ppa.launchpad.net/ubuntu-mozilla-security/ppa/ubuntu hardy main
After saving the file, you have to run:
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 7EBC211F
sudo apt-get update
sudo apt-get dist-upgrade
- You have to have an account in our tracking system. Go to http://mozilla.qa.ubuntu.com and click on “Log In” and “Create New Account”
- 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”.
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.
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!