As of today, we are exactly one month away from the release of Saucy Salamander. As part of that release, ubuntu is committed to delivering an image of ubuntu-touch, ready to install on supported devices.
And while folks have been dogfooding the images since May, many changes have continued to land as the images mature. As such, the qa team is committing to test each of the stable images released, and do exploratory testing against new features and specific packagesets.
If you have a device, I would encourage you to join this effort! Everything you need to know can be found upon this wiki page. You'll need a nexus device and a little time to spend with the latest image. If you find a bug, report it! The wiki has links to help. Testing doesn't get anymore fun than this; flash your phone and try to break it! Go wild!
And if you don't own a device? You can still help! As bugs are found and fixed, the second part of the process is to create automated tests for them so they don't occur again. Any bug you see on the list is a potential candidate, but we'll be marking those we especially think would be useful to write an autopilot tests for with a " touch-needs-autopilot" tag.
Join us in testing, confirming bugs, or testwriting autopilot tests. We want the ubuntu touch images to be the best they can be in 1 month's time. Happy Testing!
As mentioned in my last post, Mir is one of the biggest changes coming in 13.10. With feature freeze now happening this week, it's time to amp up our testing engines once more to test the final features and help land Mir into the archive.
The Mir team has put together both a ppa and wiki page that contains all the information you need to help with testing. The testing window closes in 2 days on August 28th, just in time for feature freeze. The biggest changes for Mir are the inclusion of multi-monitor support and thus are a focus for this testing. So here's the details you need to know.
Help test Mir using your current system, ubuntu saucy and the Mir team ppa.
Now through August 28th.
The full instructions for installing the ppa, running the tests, and reporting the results can be found on this wiki page. Results are reported on this page or via the package tracker testing page.
Thank you for your contributions! Good luck and Happy Testing Everyone!
So you've seen the building excitement and noise around the core apps project and are wishing there was a way for you to help. Perhaps your not a developer or someone with the skills to help write auomated tests. Or maybe you just want a preview of what things are like and play around with the developing ubuntu touch platform.
The good news is that you can! As Jono shared, we want to dogfood the core apps this month. The core apps can all be run on your ubuntu desktop, you don't need to flash a phone or tablet, and you don't even need to be running saucy (ubuntu development version). (Of course if you do have a phone, flash it and dogfood there if possible!)
Consider this text your giant disclaimer. Just a reminder these images are not intended for end-users; please don't go flashing your device thinking you'll have a replacement for android. These images are intended for developers, enthusiasts and testers who want to help. If this describes you, please read on!
I'm happy to announce the ubuntu touch images are now available for testing on the isotracker. And further, the images are now raring based! As such, the ubuntu touch team is asking for folks to try out the new images on there devices and ensure they are no regressions or other issues.
As discussed and planned, Smart Scopes have landed! Unity 7 too is landing, with many more features around getting 100 scopes installed, privacy, and dash improvements. For details on what Unity 7 is bringing, check out this post.
In support of the Unity changes, the Unity development team is asking for some extra testing on these specific features. So, we've updated and added a new testcase to our unity suite for these smart scopes. Pay attention to the cases marked mandatory and optional. The testcases relating to the smart scopes have all been marked as mandatory, and are the essential tests to run. That said, it doesn't hurt to run through the optional cases if you have time. We don't like regressions either :-)
So, here's what you need to know!
Never done a call for testing before? Read/Watch this first!; Call for testing walkthrough
Install the new unity from a ppa; Installation Instructions
Load the testcases and select one; Unity 7 Testing
Read the testcase, perform the actions listed and record your results.
If you run into any issues, please file a bug
Finally, please note the changelogs and build status found on the tracker, as well as any known bugs while testing. New builds will continue to trickle in over the next few days with new changes coming in. I'd encourage you to test and then re-test later in the week to follow-up on bugs you find, or test the new things that land.
As always please contact me if you run into issues, or have a question.
Thank you in advance for your help, and happy testing everyone!
It's the testing event I've been waiting for! A new version unity has arrived, stock full of compiz fixes. The team has removed metacity completely, and also migrated to gsettings from gconf. The result is removal of unity2d, and the enablement of llvmpipe on unity for those running without hardware acceleration.
Now, of course this work, in particular the settings migration, needs to be tested. This is where all of you come in! The package tracker now contains an entry for unity, complete with testcases for this migration. For those who helped test last cycle, you will also notice all of the checkbox testcases have been ported over as well! Many thanks to the unity developers for there help in migrating these tests. For this call for testing, the 'Unity GSetting Migration' testcases have been marked as mandatory, meaning that testcase is the primary focus. However, if you are able, executing the other testcases also helps the unity team ensure there haven't been any regressions.
Please note the 'Unity GSetting Migration' has steps for you to complete BEFORE you install from the ppa. Please read it first before diving in. Here's a link to the testing on the tracker. And if you are new, check out our wiki for a guide on using the qatracker to help test.
Now, as an added bonus, the unity developers have also tagged several multi-monitor bugs and have asked users to go through the list and confirm any bugs that they can. Read the bug report, and if you have a multi-monitor unity setup, see if it's still affecting you. Leave a comment on the bug with your result. The unity team wants to make sure the bugs are able to be triaged and get proper attention if they are still valid.
List of unity bugs, tagged multi-monitor
Thank you in advance for your help, and happy testing everyone!
As announced earlier the kernel team is looking for a some folks to help bring the 12.10 kernel to 12.04. Once 12.10 has been released, the team wants to enable newer hardware support via the kernel for the LTS version of the desktop. So, since the original announcement, we've had 10 people help test the various builds of the kernel from the ppa. Thanks so much to all who tested! Now we'd like to take this testing to the next level.
We've put together a list of commonly used hardware that we want to ensure proper support for the kernel. I'm asking for volunteers to run the kernel from the ppa on precise and report results. The catch here is that we want to have at least 1 person who has each piece of hardware listed be represented. Make sense? For example, we want folks running nvidia cards to have at least a couple people reporting results using nouveau and the proprietary driver. Same for AMD and Intel. On the wireless side, getting someone who has a chipset of each of the manufacturers listed is our goal. This is a first step in our on-going efforts to help make testing and quality a more assured and quantitative effort. We're going 'quantal' if you will. For those who want to have even more detailed and specific hardware testing, hang tight. If you'll remember this past UDS we spoke about creating a community hardware database. Work to enable this is on-going, and I hope to be able to share more about it in the coming months. In the meantime, let's build up a list of folks and systems ready to populate such a database, shall we? ;-)
So if your interested in helping, go ahead and edit that wiki page. Add yourself under one or more pieces of hardware. There's a handy script that should help you identify what's in your system if your not quite sure. Then head over to the QATracker.
Once there click on 'Quantal kernel for precise LTS', you will wind up on a page showcasing the tests and instructions for this call for testing. If you click the on 'Link to the installation information' you will get information on installing and uninstalling the package. Similarly the 'Link to bug reporting instructions' provides details on reporting a bug you find in the test case. Finally, if you click 'Kernel Smoke Tests' you'll arrive on the page to report your testcase results. Note you will need to sign in using your ubuntu sso account to report results.
If you encounter issues, you can always reboot into your current working kernel and be back to normal. As always, if you have any issues in using the tracker, feel free to get in touch with me.
EDIT: This has been migrated to the production instance. Check out the new post here to get invovled.
The first calls for testing for this cycle are happening! I am excited to not only announce the opportunity to help test this new kernel, but also to unveil some of the new features to the qatracker to allow us to better serve our needs for calls for testing.
Last cycle, calls for testing was a manual thing -- I asked, and the community responded, following along using instructions from a blog or mailing list post. Now we're going to put some more structure around this as I spoke about earlier.
The kernel team is committing to keeping precise up-to-date by providing kernels from the future releases in precise. The first one of these will be the 12.10 kernel which will land in precise as part of the normal 12.04.X update. In order for that to happen, the team is making available kernels to test on 12.04. If you need a newer kernel for hardware enablement, this is the kernel you are encouraged to run and report on. For those running the mainline kernel, this differs in that the ubuntu patchset and official support for this kernel running on 12.04 will happen when it is pushed via update.
So we're really testing a couple things here -- the 12.10 kernel on 12.04, but also the new qatracker. Feedback is encouraged on the qatracker also! Ok, so how does this work?
First, you'll need to use the staging site for the qatracker, were a package tracker has been setup. If you click on the 'Quantal kernel for precise LTS' link, you will wind up on a page showcasing the tests and instructions for this call for testing. If you click the 'Link to the installation information' link you will get information on installing and uninstalling the package and filing bugs against the package. Especially note the instructions for filing a bug properly; additional information is requested to help make your bug report more helpful to the development team. If you click the 'Kernel Smoke Tests' link you'll arrive on the page with the instructions for the testcase. If you login to the tracker using your ubuntu SSO credentials, you will be able to report results as well. This should look very familiar to those of you who have used the isotracker in the past. Neat eh? If you have any issues in using the tracker, feel free to get in touch with me.
I'm asking those folks willing to help test please head over to the qatracker and submit results. Note that the qatracker emails are turned off, but otherwise everything should function as expected for you. To leave feedback on the new site, file a bug and mention your using the new staging qatracker. Contributions to the qatracker are welcome and encouraged, contact me if your interested in helping out.
Sprinting in to the finish! Unity 5.8 saw the introduction of the sticky edge being able to be turned off, and the addition of being able to control where the launcher appeared on which monitors. Unity 5.10 has been released into the team's ppa. This release has been about bugfixes and polish as the precise cycle winds down to a close. Still, there are some notables changes:
Jorge Castro and Mark Shuttleworth have both blogged about MAAS, or metal as a service and what it means for ubuntu and the server community. The development team is eager to get folks out there testing, using and giving feedback on MAAS, and have created a series of checkbox tests to help do so.
Check out this page on the wiki for more information. In short, if you've done any unity testing or manual app testing this cycle you will feel right at home.
When you respond 'no' to a checkbox test, apport should automatically launch and guide you through the bug filing process.
If you'd like to give feedback, comments or even patches, get in touch with the team on launchpad at https://launchpad.net/~maas-devel.
Don't hesitate to reach out to the wonderful folks on MAAS Team, the MAAS devel mailing list, or on IRC #ubuntu-server on freenode. Thanks for helping test ubuntu!
We're getting closer! The unity design list has been ablaze with discussions on unity recently. It's been great to watch and read. With that in mind, the unity developers have pushed out another point release for us to preview and test. Here's what's new:
As beta1 for precise draws closer and closer, it's time for testing some new stuff. On the docket is wubi, everyone's favorite way to get ubuntu without having to worry about disk partitioning or losing there current windows installation. Wubi was created out of a desire to lower the barrier of entry for newcomers to ubuntu. So, if you want to help create a wonderful experience for those new users, I would encourage you to help test wubi. The testing window for this goes through the weekend, as the first iso spins will be happening on Monday for iso testing :-)
Prerequisites: You will need access to a computer that has windows xp or higher installed on it. In addition, the computer will need at least 5 gb of free disk space. As always, make sure you have backups and can restore the computer if required.
1) Download a current daily image (http://cdimage.ubuntu.com/daily-live/current/). You can chose a 32-bit or 64-bit desktop cd.
2) Burn the iso you downloaded. If you need help burning the iso, check out this handy wiki article: https://help.ubuntu.com/community/BurningIsoHowto
3) Boot up the windows computer.
Once you have the cd and the windows computer is booted you can run through the testcases. For this round, we're focusing on 2 tests; wdi-001 and wdi-002. Check out the wiki page and follow the instructions for each case. http://testcases.qa.ubuntu.com/Install/DesktopWubi
Once you've gone thru both testcases you should have a working ubuntu install alongside your windows installation.
Did everything work? Leave me a comment below and let me know about it. Failed? Check out how to file a bug below.
Please file bugs against the wubi package in launchpad (https://bugs.launchpad.net/wubi/+filebug). When filing, please make sure to tag your bug 'beta1'.
If you'd like to give feedback, comments or even patches, get in touch with the team on launchpad at https://launchpad.net/wubi.
Don't hesitate to reach out to the wonderful folks on launchpad on the wubi team, the ubuntu+1 forums, or myself if you have questions. Thanks for helping test ubuntu!
The upstart team has a new version of upstart that is pending for precise, and would like some feedback on it. The timeline on this is very short (ending Feb 15th), but the team would appreciate any testing that is completed. The shiny new stuff in this release includes:
Another couple weeks, and another Unity point release. The unity developers have been doing a great job of shipping us updates to try out on a regular cycle. Kudos to them. This means you and I get to preview the coming attractions and help test.
Unity 5.4 sees the reunion of HUD and unity again. This means HUD is going to be getting exposed to everyone running precise after this round of testing. You'll also happily notice the HUD has a much more appealing theme and set of testcases!
Prerequisites: Make sure you are running the latest version of precise, and all your packages are up to date. Unfortunately this cannot be installed on oneiric or any previous ubuntu release.
1) Add the unity ppa (https://launchpad.net/~unity-team/+archive/ppa). You can do this by issuing the following command:
sudo add-apt-repository ppa:unity-team/ppa
2) Update apt and run a dist upgrade -- this should prompt you to upgrade unity and some indicators as well as install checkbox-unity.
sudo apt-get update && sudo apt-get dist-upgrade
3) Restart your unity session by logging out and logging back in again.
Ok, hopefully the upgrade went smooth for you, but if not, head over to freenode #ubuntu-unity channel and let folks know what went wrong.
So, now that your up and running you can run the through the manual tests the unity team has prepared. Open the dash and type 'unity testing'. The Checkbox Unity Tests should launch. Checkbox will gather some information on your system and then ask you which tests you wish to run. Once complete you will see a link containing your system report and an option to publish it to launchpad. Use the text box below the link to enter your launchpad email address and then hit submit. This will ensure your results and feedback go to the unity developers.
Please ensure you have finished and submitted your testing results ASAP. As usual, the testing window will be closed this Thursday at 8am UTC, in order to give the unity developers time to finish fixing the bugs found. Then Unity 5.4 will be pushed to precise.
Please file bugs against unity package in launchpad (https://bugs.launchpad.net/unity/+filebug). When filing, please make sure to tag your bug '5.4-rc1' and mention your running Unity 5.4-rc1 in your description.
If you'd like to give feedback on design for unity, Check out the awesome http://unity.ubuntu.com/getinvolved/ site. If your wanting to contribute code or patches, visit the folks on the #ubuntu-unity on freenode.
Don't hesitate to reach out to the wonderful folks on freenode @ #ubuntu-unity, the unity web site, the ubuntu+1 forums, or myself if you have questions. Thanks for helping test ubuntu!
ALSA 1.0.25 was recently released, and has now been packaged and placed into the ubuntu audio dev ppa. The new alsa-utils needs tested for breakage before releasing into the archive. Note that the new version of alsa-lib is already in the precise archive.
The changes in this new version are detailed on the ALSA site. Check them out. In particular ARM support has changed, so for anyone with ARM hardware it would get wonderful for you to test and make sure nothing is broken.
The timeline for testing alsa-utils is until Feburary 16th, so it can be finalized by the feature freeze for precise.
Prerequisites: Please make sure you are running the latest version of precise, and all your packages are up to date.
1) Add ubuntu audio dev ppa (https://launchpad.net/~ubuntu-audio-dev/+archive/ppa). You can do this by issuing the following command:
sudo apt-add-repository ppa:ubuntu-audio-dev/ppa
2) Update apt and run a dist upgrade -- this should prompt you to upgrade alsa-utils.
sudo apt-get update && sudo apt-get dist-upgrade
3) Restart your unity sessions by logging out, and then logging back in
Can't hear any sounds now? You may need to recover your system using ppa-purge and then file a bug on what went wrong.
Can you still hear sounds? If so, also check the following items to make sure nothing is broken:
Try rebooting your system. Can you still hear audio?
Ensure the /var/lib/alsa sound state files exists. Enter this command:
Do you see an asound.state file?
Are you using jack or another plugin from the alsa-plugins package? Is everything working correctly?
Does the libasound2-plugins documentation match up to the existing plugins provided?
If you find something is broken, please let the developers know. Please file bugs against the applicable alsa package in launchpad.
Make sure when filing to tag it "alsa-1.0.25", and mention you are testing from the ubuntu audio dev ppa. This will make sure your issue is seen by the developers and they will know it is in relation to this new package.
Feel free to provide any comments or feedback to the ubuntu-devel mailing list or by sending a message to TheMuso or diwicon on freenode @ #ubuntu-devel.
Submitting a patch
Got a fix for something broken? Submit your merge proposals to the ubuntu audio dev ppa. The ubuntu audio dev team would love to hear about them.
Don't hesitate to reach out to the wonderful folks on freenode @ #ubuntu-devel, the ubuntu-devel mailing list, the ubuntu+1 forums, or myself if you have questions. Thanks for helping test ubuntu!
The ubuntu desktop team has packaged up a new version of compiz and is looking for people to help test for breakage before releasing into the archive. The testing will be taking place over the weekend, with early next week set as the target date for pushing the changes into the archive (including fixes for any bugs you may find! :-) ).
The changes in this new version of compiz are better performance and stability, but this needs testing to verify that is the case.
Prerequisites: Please make sure you are running the latest version of precise, and all your packages are up to date. Unfortunately this cannot be installed on oneiric or any previous ubuntu release. PLEASE MAKE SURE YOU ARE COMFORTABLE WITH RECOVERING YOUR SYSTEM WITHOUT A GUI. This may break unity and you may need to recover via the command line.
1) Add didrocks ppa (https://launchpad.net/%7Edidrocks/+archive/ppa). You can do this by issuing the following command:
sudo add-apt-repository ppa:didrocks/ppa
2) Update apt and run a dist upgrade -- this should prompt you to upgrade compiz.
sudo apt-get update && sudo apt-get dist-upgrade
3) Restart your computer
Ok, hopefully the upgrade went smooth for you, but if not, you may need to recover your system using ppa-purge and then file a bug on what went wrong. You may need to enter a VT session (ctrl+alt+f2 for example) and downgrade back to a stable version of compiz (using ppa-purge) and then reboot as your unity desktop likely won't come up in the event something didn't work.
Ok, so hopefully your rebooted PC brought you back to your unity desktop. Congratulations, you've done quite a bit of testing already! For this package, the rest of the testing is very generalized. Go about your normal workflow and see if you encounter any issues. For instance;
Did your pc report any weird errors while booting? (check the syslog, dmesg, etc)
Are you seeing any new UI rendering bugs?
Perhaps some of your compiz settings are no longer working?
If you find something is broken, please let the developers know. Please file bugs against the compiz-core package in launchpad (https://bugs.launchpad.net/compiz-core/+filebug). Make sure when filing to tag it "0.9.7.0-beta1". This will make sure your issue is seen by the developers and they will know it is in relation to this new package.
Feel free to provide any comments or feedback to the ubuntu desktop mailing list, or to the folks on freenode @ #ubuntu-unity.
Don't hesitate to reach out to the wonderful folks on freenode @ #ubuntu-unity, the ubuntu desktop mailing list, the ubuntu+1 forums, or myself if you have questions. Thanks for helping test ubuntu!
© 2010 Canonical Ltd. Ubuntu and Canonical are registered trademarks of Canonical Ltd.