LoCos

Differences between revisions 1 and 22 (spanning 21 versions)
Revision 1 as of 2009-11-30 13:47:57
Size: 6
Editor: 63
Comment:
Revision 22 as of 2010-03-26 22:25:54
Size: 4314
Editor: c-24-130-24-116
Comment: update for Beta 2
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
TBA <<Include(Testing/Header)>>
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||

{{{#!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
}}}

== How can I help? ==


'''Lucid Lynx Beta 2 is coming [[https://wiki.ubuntu.com/LucidReleaseSchedule|Thursday, Apr 8th]].'''

'''Lucid ISO Testing begins Tuesday, Apr 6th'''

 * ISO Testing [[http://ubuntutesting.wordpress.com/2009/09/21/old-friend-iso-testing-tracker/|overview]] & Open Week [[MeetingLogs/openweekKarmic/TestISOs|session]] - pre-release testing of Ubuntu images
   * [[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/.
   * zsync will greatly [[http://ubuntu-tutorials.com/2009/10/29/use-zsync-to-update-existing-iso-images/|speed up downloads]] of iso images
 * join '''#ubuntu-testing''' on freenode.net
 * join [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa|ubuntu-qa]] for discussion
 * Please forward testing related announcements to your LoCo.
 * [[QATeam/Meetings|Weekly IRC 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: [[https://bugs.launchpad.net/ubuntu/+source/virtualbox-ose/+bug/508777|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: [[UbuntuDevelopment/UsingDevelopmentReleases|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 [[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.

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

== Working with the Ubuntu Community ==

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.

== 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.

IconsPage/iconCircle48.png

Quality Team

Calendar

Hackfests & Calendar

Cadence Schedule

Roles

Contacts

Contact

Contacts

FAQ


How can I help?

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

Lucid ISO Testing begins Tuesday, Apr 6th

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)