LoCos

Differences between revisions 12 and 32 (spanning 20 versions)
Revision 12 as of 2009-12-07 21:33:55
Size: 3422
Editor: adsl-68-127-160-101
Comment: releases link, text from the email
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 4: Line 4:
{{{#!wiki comment/dotted
 */ TODO: move some of this content to the front page so it's more visible to everyone (and not just people who click loco) */

Let's get merging done or not. Is anyone actively working on this merging? Email me. Grant
}}}
Line 6: Line 12:
'''Lucid Lynx Alpha 1 is coming [[https://wiki.ubuntu.com/LucidReleaseSchedule|Thursday, Dec 10th]].'''
Line 8: Line 13:
'''Lucid ISO Testing begins Tuesday, Dec 8th''' '''Ubuntu 11.04 (Natty Narwhal) Beta 1 is coming [[https://wiki.ubuntu.com/NattyReleaseSchedule|Thursday, March 31st]].'''

'''ISO Testing begins Tuesday, Mar 29th'''
Line 11: Line 18:
   * [[https://launchpad.net/~testdrive|Testdrive]] automates the use of kvm or virtualbox, saving its image to ~/.cache/testdrive/.
Line 12: Line 20:
 * Upgrade Testing - please report bugs that may not be revealed in [[http://people.ubuntu.com/~mvo/automatic-upgrade-testing/|automated testing]]
Line 13: 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
 * Please forward testing related announcements to your LoCo.
Line 16: Line 26:
 * [[LaptopTestingTeam]] helping users share their experiences with hardware like theirs.

''' PLEASE NOTE: [[UbuntuDevelopment/UsingDevelopmentReleases|Development Releases]] are not for daily use! These releases will contain bugs. You have been warned.'''
 * [[Testing/Laptop|Laptop Testing Project]] helps users share their experiences with hardware like theirs.
 * Bugs that prevent testing: ... ?
 * Stable Release Updates (SRU) are packages about to be released officially. If you would like to help please see [[QATeam/PerformingSRUVerification]]
''' PLEASE NOTE: [[UsingDevelopmentReleases|Development Releases]] are not for daily use! These releases will contain bugs. You have been warned.'''
Line 22: 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 28: Line 39:
Approved and "new" [[LoCoTeamList|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 help begin test Ubuntu. Approved and "new" [[LoCoTeamList|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.
Line 32: 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.

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)