LoCos

Differences between revisions 21 and 32 (spanning 11 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 32 as of 2012-12-21 09:43:58
Size: 4294
Editor: javier-lopez
Comment:
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]].''' '''Ubuntu 11.04 (Natty Narwhal) Beta 1 is coming [[https://wiki.ubuntu.com/NattyReleaseSchedule|Thursday, March 31st]].'''
Line 15: Line 15:
'''Lucid ISO Testing begins Tuesday, Mar 16th''' '''ISO Testing begins Tuesday, Mar 29th'''
Line 18: Line 18:
   * [[https://launchpad.net/~testdrive|Testdrive]] (after adding [[https://launchpad.net/~testdrive/+archive/ppa|PPA]]) automates the use of kvm or virtualbox, saving it's image to ~/.cache/testdrive/.    * [[https://launchpad.net/~testdrive|Testdrive]] automates the use of kvm or virtualbox, saving its image to ~/.cache/testdrive/.
Line 20: Line 20:
 * Upgrade Testing - please report bugs that may not be revealed in [[http://people.ubuntu.com/~mvo/automatic-upgrade-testing/|automated testing]]
Line 21: Line 22:
 * join [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa|ubuntu-qa]] for discussion  * join [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality|ubuntu-quality]] for discussion
Line 25: Line 26:
 * [[LaptopTestingTeam]] helping users share their experiences with hardware like theirs.
 * Bugs that prevent testing: [[https://bugs.launchpad.net/ubuntu/+source/virtualbox-ose/+bug/508777|virtualbox-ose bug 508777]] (workaround is using F6 during boot to disable acpi)
 * [[Testing/Laptop|Laptop Testing Project]] helps users share their experiences with hardware like theirs.
 * Bugs that prevent testing: ... ?
Line 28: Line 29:
''' PLEASE NOTE: [[UbuntuDevelopment/UsingDevelopmentReleases|Development Releases]] are not for daily use! These releases will contain bugs. You have been warned.''' ''' PLEASE NOTE: [[UsingDevelopmentReleases|Development Releases]] are not for daily use! These releases will contain bugs. You have been warned.'''
Line 32: Line 33:
This page is part of a conscious effort by Ubuntu [[QATeam|Quality Assurance]] Team ([[https://launchpad.net/~ubuntu-qa|lp]]) and [[Testing]] Team ([[https://launchpad.net/~ubuntu-testing|lp]]) to increase participation of the Ubuntu community and especially !LoCo teams in testing. The [[Roadmaps/Lucid/TestingTeam|roadmap]] and [[https://blueprints.launchpad.net/ubuntu/+spec/lucid-qa-testing-team|blueprint]] from UDS describe these efforts. This page is part of a conscious effort by Ubuntu [[QATeam|Quality Assurance]] Team ([[https://launchpad.net/~ubuntu-qa|lp]]) and [[Testing]] Team ([[https://launchpad.net/~ubuntu-testing|lp]]) to increase participation of the Ubuntu community and especially !LoCo teams in testing. The older Lucid UDS [[Roadmaps/Lucid/TestingTeam|roadmap]] and [[https://blueprints.launchpad.net/ubuntu/+spec/lucid-qa-testing-team|blueprint]] describe the beginning of these efforts.
Line 42: Line 43:
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. A benefit of using open source software is the ability to participate in its 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.

IconsPage/iconCircle48.png

Quality Team

Calendar

Hackfests & Calendar

Cadence Schedule

Roles

Contacts

Contact

Contacts

FAQ


How can I help?

Ubuntu 11.04 (Natty Narwhal) Beta 1 is coming Thursday, March 31st.

ISO Testing begins Tuesday, Mar 29th

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 older Lucid UDS roadmap and blueprint describe the beginning of 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 its 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)