Differences between revisions 21 and 24 (spanning 3 versions)
Revision 21 as of 2010-02-26 02:28:03
Size: 4316
Editor: adsl-68-127-173-151
Comment: preparing for beta 1, not sure what to do about merging elsewhere. I'm open but the comment is very old and hasn't been acted on.
Revision 24 as of 2010-04-07 13:38:14
Size: 4509
Editor: adsl-68-127-147-123
Comment: syntax fix - I need to use preview more
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
'''Lucid Lynx Beta 1 is coming [[https://wiki.ubuntu.com/LucidReleaseSchedule|Thursday, Mar 18th]].''' '''Lucid Lynx Beta 2 is coming [[https://wiki.ubuntu.com/LucidReleaseSchedule|Thursday, Apr 8th]].'''
Line 15: Line 15:
'''Lucid ISO Testing begins Tuesday, Mar 16th''' '''Lucid ISO Testing begins Tuesday, Apr 6th'''
Line 20: Line 20:
 * Upgrade Testing - Ubuntu 10.04 LTS has extra upgrade testing - please report bugs that may not be revealed in [[http://people.ubuntu.com/~mvo/automatic-upgrade-testing/|automated testing]]
Line 23: Line 24:
 * [[QATeam/Meetings|Weekly IRC meetings]] Wednesdays at 17.00 UTC in #ubuntu-meeting  * [[QATeam/Meetings|Weekly IRraC meetings]] Wednesdays at 17.00 UTC in #ubuntu-meeting

How can I help?

Lucid Lynx Beta 2 is coming Thursday, Apr 8th.

Lucid ISO Testing begins Tuesday, Apr 6th

  • ISO Testing overview & Open Week session - pre-release testing of Ubuntu images

    • Testdrive (after adding PPA) automates the use of kvm or virtualbox, saving it's image to ~/.cache/testdrive/.

    • zsync will greatly speed up downloads of iso images

  • Upgrade Testing - Ubuntu 10.04 LTS has extra upgrade testing - please report bugs that may not be revealed in automated testing

  • join #ubuntu-testing on freenode.net

  • join ubuntu-qa for discussion

  • Please forward testing related announcements to your LoCo.

  • Weekly IRraC meetings Wednesdays at 17.00 UTC in #ubuntu-meeting

  • Thursdays UbuntuBugDay in IRC #ubuntu-bugs

  • LaptopTestingTeam helping users share their experiences with hardware like theirs.

  • Bugs that prevent testing: virtualbox-ose bug 508777 (workaround is using F6 during boot to disable acpi)

  • Stable Release Updates (SRU) are packages about to be released officially. If you would like to help please see QATeam/PerformingSRUVerification

PLEASE NOTE: Development Releases are not for daily use! These releases will contain bugs. You have been warned.

Who is involved?

This page is part of a conscious effort by Ubuntu Quality Assurance Team (lp) and Testing Team (lp) to increase participation of the Ubuntu community and especially LoCo teams in testing. The roadmap and blueprint from UDS describe these efforts.

All Ubuntu Releases are included such as Kubuntu, Xubuntu and Edubuntu.

Working with the Ubuntu Community

Approved and "new" Local Community teams are natural partners in the testing process. As advocates and active users we know about the software and the perception of Ubuntu by people who are not computer experts. This perspective is extremely valuable. We hope this page provides a clear and concise jumping off point for active teams and users to learn the skills and procedures needed to test Ubuntu.

Why Test?

A benefit of using open source software is the ability to participate in it's development. Contributions to the projects that Ubuntu distributes is encouraged, however most people are first introduced to a software package by using it. Every user can be seen as a software tester. Sometimes problems are noticed that can be reported. Open source software fundamentally depends upon people participating. You are in good company because an incredibly large and growing number of people do participate every day from all parts of the world. If nobody steps forward to report issues then busy, well intentioned developers may inadvertently overlook these unintended features in the software they provide.

There is an art/science to knowing how and where to report these problems. It takes effort to isolate an issue so that one of the various parties involved can fix it, though this gets easier with practice. A great feeling of satisfaction can be found when reporting problems and seeing them fixed. While the daily work of quality assurance can be under appreciated, experienced developers recognize the value of good bug reports and are very grateful.

Testing/LoCos (last edited 2012-12-21 09:43:58 by javier-lopez)