LoCos

Differences between revisions 2 and 11 (spanning 9 versions)
Revision 2 as of 2009-12-03 23:34:59
Size: 2196
Editor: nat
Comment: first draft - I may have gone overboard with contextual description - maybe split into a "why testing" page?
Revision 11 as of 2009-12-07 21:30:37
Size: 3343
Editor: adsl-68-127-160-101
Comment: can't forget the warning about UsingDevelopmentReleases
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
<<Include(Testing/Header)>>
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||

== How can I help? ==

'''Lucid Lynx Alpha 1 is coming [[https://wiki.ubuntu.com/LucidReleaseSchedule|Thursday, Dec 10th]].'''

'''Lucid ISO Testing begins Tuesday, Dec 8th'''

 * 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
   * 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
 * [[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.

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

== 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 help begin test Ubuntu.

== Why Test? ==
Line 3: Line 32:
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. 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.

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 test Ubuntu.

'''Lucid Lynx Alpha One is coming [[https://wiki.ubuntu.com/LucidReleaseSchedule|Dec 12th]].'''

 * 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 - begin testing Dec 7th

 * [[QATeam/Meetings|Weekly IRC meetings]] Wednesdays at 17.00 UTC on #ubuntu-meeting


This page is part of a conscious effort by Ubuntu to increase participation with !LoCo teams. The [[Roadmaps/Lucid/TestingTeam|roadmap]] and [[https://blueprints.launchpad.net/ubuntu/+spec/lucid-qa-testing-team|blueprint]] from UDS describe these efforts.
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.

How can I help?

Lucid Lynx Alpha 1 is coming Thursday, Dec 10th.

Lucid ISO Testing begins Tuesday, Dec 8th

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.

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 help begin 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)