Testing

Differences between revisions 3 and 43 (spanning 40 versions)
⇤ ← Revision 3 as of 2013-07-22 14:23:38 →
Size: 7675
Editor: 2
Comment:
← Revision 43 as of 2014-01-06 22:22:16 → ⇥
Size: 8010
Editor: bba74651
Comment: Adding https://wiki.ubuntu.com/Bugs/Upstream/GNOME
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
COMING SOON! <<Include(UbuntuGNOME/Header)>>
<<BR>>
##||<tablestyle="width: 95%; margin: 5px 0;" style="border: none; border-radius: 10px; background-color: #b7d1ea; font-size: 0.90em;" :> '''[Announcement] [[http://ubuntugnome.org/ubuntu-gnome-trusty-tahr-14-04-alpha-1 | Ubuntu GNOME Trusty Tahr Alpha 1]] has arrived''' ||
Line 3: Line 5:
'''Go Back to [[https://wiki.ubuntu.com/UbuntuGNOME | Home Page]]''' ||<tablestyle="width: 95%; margin: 5px 0;" style="border: none; border-radius: 10px; background-color: #e9c6af; font-size: 0.90em;" :> '''We are now testing Ubuntu GNOME Trusty Tahr [[http://cdimage.ubuntu.com/ubuntu-gnome/daily-live/current | Daily Builds]]''' ||
<<BR>>
Line 6: Line 9:
<<BR>>
Line 8: Line 12:
||<tablestyle="width: 55%; margin: 5px 0;" style="border: none; border-radius: 10px; background-color: #ffffcc; font-size: 0.90em;" :>'''"Testing is an infinite process of comparing the invisible to the ambiguous in order to avoid the unthinkable happening to the anonymous." - James Bach''' ||
<<BR>>
Line 11: Line 16:
== Before Getting Started ==
Testing and using Development Releases of Ubuntu GNOME (or any other flavor of Ubuntu) isn't meant to be for production machines of daily usage. Testing is to make sure the Stable Release is working as good as possible. Find Bugs, Improve Performance, etc - this is what we do until we finalize the testing process and release a stable version. Whenever you are testing, keep in mind few notes:
Line 12: Line 19:
'''13.10 Alpha 1 has now been released, we are now back on the dailies.'''  1. Make sure to [[https://help.ubuntu.com/community/BackupYourSystem | Backup]] your '''important data'''. If you are using Linux, the best and easier way is to make a copy of your '''/home''' folder or partition. If you want to do a full system backup, please see [[https://help.ubuntu.com/community/BackupYourSystem | this link]] and [[http://www.howtogeek.com/108869/how-to-back-up-ubuntu-the-easy-way-with-dj-dup/ | this link too]].
 1. You can use [[http://en.wikipedia.org/wiki/Virtual_machine | Virtual Machines]] - for example [[https://help.ubuntu.com/community/VirtualMachines | See this]]. You can use USB Drives or External HDD. You can use your machine. That is totally up to you but please, refer to #1 :)
 1. Using a Development Release is not suitable for daily production machine.
 1. The more you break your installation, the better. That is why, to play it safe, better to use Virtual Machines, Spare Testing Machines and/or USB Drives, specially with Alpha 1 and Alpha 2. Beta Releases are a bit more stable but still under heavy development.
 1. '''The most important part of testing is to actually install the system and check how the installation process will work'''. This is very important. Also, if you have say Alpha 1 installed, it is less helpful to just upgrade it to Alpha 2 or Beta 1. Please, do a fresh new install - you can either [[https://help.ubuntu.com/community/ZsyncCdImage | zsync]] your ISO or download again.
 1. Finally, always remember: '''Better Safe Than Sorry''' :)
Line 14: Line 26:
For Ubuntu GNOME Saucy Daily Build, please see [[http://cdimage.ubuntu.com/ubuntu-gnome/daily-live/current/ | this]]. == Start Testing ==
||<tablestyle="width: 95%; margin: 5px 0;" style="border: none; border-radius: 10px; background-color: #d7f4d7; font-size: 0.90em;" :> [[http://ubuntugnome.org/ubuntu-gnome-trusty-tahr-14-04-alpha-1 | Ubuntu GNOME Trusty Tahr Alpha 1]] has been released ||

||<tablestyle="width: 95%; margin: 5px 0;" style="border: none; border-radius: 10px; background-color: #afe9af; font-size: 0.90em;" :> Ubuntu GNOME Trusty Tahr Alpha 2 is coming soon! ||

||<tablestyle="width: 95%; margin: 5px 0;" style="border: none; border-radius: 10px; background-color: #f4d7d7; font-size: 0.90em;" :> ▶ '''Please help us to test: [[http://ubuntugnome.org/ubuntu-gnome-trusty-tahr-14-04-alpha-1 | Ubuntu GNOME Trusty Tahr Daily Build]]''' ||

||<tablestyle="width: 95%; margin: 5px 0;" style="border: none; border-radius: 10px; background-color: #d5e5ff; font-size: 0.90em;" :> See: [[https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule | Trusty Tahr Release Schedule]] ||

## * '''The Pre-alphas for trusty are now on Daily Builds'''

##Nothing major has yet happened, but do check once in a while as they do tend to get broken at this stage! The quicker such problems are spotted, the easier it is for the developers to track back to what broke. Head over to '''[[http://cdimage.ubuntu.com/ubuntu-gnome/daily-live/current/ | Daily Builds]]''' to grab one.

## * Download Ubuntu GNOME Saucy Daily Build, please see [[http://cdimage.ubuntu.com/ubuntu-gnome/daily-live/current/ | This Link]].
Line 18: Line 43:
##Please read the [[https://wiki.ubuntu.com/SaucySalamander/Alpha1/Lubuntu | release notes for Alpha 1]]. ## * Download Ubuntu GNOME Saucy Beta 2, please see [[http://cdimage.ubuntu.com/ubuntu-gnome/releases/saucy/beta-2/ | this link]].

## * Please read the [[https://wiki.ubuntu.com/SaucySalamander/Beta2/UbuntuGNOME | release notes for Beta 2]].
Line 21: Line 49:
== Getting Involved ==
=== Join Ubuntu GNOME QA Sub-Team ===
||<tablestyle="width: 40%; margin: 5px 0;" style="border: none; border-radius: 10px; background-color: #ffccaa; font-size: 0.90em;" :> '''[[https://launchpad.net/~ubuntugnome-qa | Ubuntu GNOME QA Team]]''' ||
Line 22: Line 53:
||<tablestyle="width: 40%; margin: 5px 0;" style="border: none; border-radius: 10px; background-color: #ffe6d5; font-size: 0.90em;" :> More information on '''[[https://wiki.ubuntu.com/UbuntuGNOME/GettingInvolved | Getting Involved Page]]''' ||
Line 23: Line 55:
== Use Raring iso's == === I am NEW to Testing, How Can I help? ===
Congratulation, you are the best and perfect candidate who actually can help us testing a development release. If you are new to all this, please read '''[[https://wiki.ubuntu.com/Testing/ISO/Walkthrough | this page]]'''. If you have any question, join the mailing list and just ask :)
Line 25: Line 58:
To save downloading the whole iso again for saucy, simply copy your raring image of what ever architecture replacing 'raring' with 'saucy' and use zsync. (You can, of course, simply do a '''mv''', but I like to keep my older iso's handy). === Ubuntu GNOME QA Mailing List ===
Once you join Ubuntu GNOME QA Sub-Team, automatically, you will be subscribed to the mailing list of Ubuntu GNOME QA Team and this is the address:
ubuntugnome-qa@lists.launchpad.net
Line 27: Line 62:

== Getting Involved ==

Please do join our [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-gnome | Mailing List]] and when you compose New Email, please write '''[Testing]''' in your subject so everyone on the list will understand what your email is all about - that you are a tester and helping out.

##Maybe we do need to create Ubuntu GNOME QA Sub-Team in case we will have more testers joining in.


## == Announcements ==

## There is a weekly digest of the test version available at ##
## [https://wiki.ubuntu.com/Lubuntu/ReleaseStatus/Raring | Release Status]]. It is updated each Friday. If you ## wish for anything to be included or have questions, please contact [[gilir]] by Thursday at the latest.

## At each milestone release, the notes at
## [[https://wiki.ubuntu.com/QuantalQuetzal/TechnicalOverview | technical overview]] are updated.		 === Share Your Findings or Ask Qs ===
It is '''VERY''' important to share your findings with the team. Also, you can ask anything on the mailing list as well. So, it is a must-do step :)
Line 44: Line 66:
||<tablestyle="width: 40%; margin: 5px 0;" style="border: none; border-radius: 10px; background-color: #ffaaaa; font-size: 0.90em;" :> '''[[https://wiki.ubuntu.com/QATeam/Overview/#Bugs | All about bugs]]''' ||
Line 45: Line 68:
Please head over to '''[[https://wiki.ubuntu.com/QATeam/Overview/#Bugs | All about bugs]]''' for further information on how bug reporting works and why it is so important. ||<tablestyle="width: 40%; margin: 5px 0;" style="border: none; border-radius: 10px; background-color: #ffd5d5; font-size: 0.90em;" :> '''[[https://help.ubuntu.com/community/ReportingBugs | How to Report Bugs]]''' ||
Line 47: Line 70:
||<tablestyle="width: 40%; margin: 5px 0;" style="border: none; border-radius: 10px; background-color: #ffaaaa; font-size: 0.90em;" :> '''[[https://wiki.ubuntu.com/Bugs/Upstream/GNOME | Upstream GNOME Bugs]]''' ||
Line 48: Line 72:
== Testing ==
Testing is split into distinct, but joined areas. The '''Daily Builds''', the '''QA-testing of Milestone releases''' and the '''Milestone releases''' themselves.		 == Testing FAQs ==
||<tablestyle="width: 40%; margin: 5px 0;" style="border: none; border-radius: 10px; background-color: #cccccc; font-size: 0.90em;" :> Please head over '''[[https://wiki.ubuntu.com/QATeam/FAQ | QA/Testing FAQs]]''' ||
Line 51: Line 75:
To not get overly complicated, think of it as that we have a [[https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule | schedule]] to keep to. A few days before a Milestone is due, the daily is plucked and becomes the QA (Quality Assurance) test version for the Milestone release. Once it is confirmed that the QA version works, it then becomes the [[https://wiki.ubuntu.com/Lubuntu/Testing#Milestone_Releases | Milestone]]. ##= Use Raring ISOs =
##To save downloading the whole iso again for saucy, simply copy your raring image of what ever architecture ##replacing 'raring' with 'saucy' and use zsync. (You can, of course, simply do a '''mv''', but I like to keep ##my older iso's handy).
Line 53: Line 78:
All release stages are tracked by [[http://iso.qa.ubuntu.com/ | ISO Tracker]] where you can get the latest builds, see and allocate any [[https://wiki.ubuntu.com/Lubuntu/ReportingBugs | Bugs]].

So, in order of how they happen.

=== Daily Builds ===

These iso's are automatically generated every 24 hours using the latest updates on the system from the devs. They are available from [[http://iso.qa.ubuntu.com/|ISO tracker]]. Using the [[https://help.ubuntu.com/community/ZsyncCdImage | zsync (or rsync)]] option allows you to update your [[https://help.ubuntu.com/community/BurningIsoHowto |iso]] to any of the various dailies you choose to follow without having to re-download the entire iso. They are there to check that bugs that are resolved between the Milestone releases do not break the install. They also are used to confirm that any fix for a bug that seriously affects an initial install which is released for testing now works. Daily builds are suspended when pre-milestone testing is being carried out (see below).

==== When do they build? ====

The Alternates are scheduled to start at 16:29 (UTC) and take approximately 30 - 45 minutes to complete.

The Desktops are also kicked off at this time, but take approximately 90 minutes to complete.

The armfh-ac100 is started at 01:35 (UTC) and should take approximately 30 minutes to complete.


''Please note from the release team: Sure, as long as it's clear that it's subject to change - We're not intending to make any promises here. We won't change them around frivolously or anything but it's possible.''

The timing of the auto build of lubuntu can be found [[http://bazaar.launchpad.net/~ubuntu-cdimage/ubuntu-cdimage/mainline/view/head:/etc/crontab | here ]]. If you do notice that builds are not appearing as expected, please contact [[phillw]] to let him know.

=== QA testing of Milestone releases ===

Cadence, Beta and Release Candidates (RC) are also tested using [[http://iso.qa.ubuntu.com/|ISO tracker]]. If you want to help out in this important area of testing, please read through [[https://wiki.ubuntu.com/Testing/ISO/Procedures | Procedures]] for further details. These appear a couple of days before the actual Milestone release so that we can check they are okay to become Milestone releases.

'''QA testing is to ensure the actual install iso works, if you can, please get involved in the qa testing'''

==== Rebuilding a Release Candidate ====

These are carried out manually, during this time the release team do update the [[http://iso.qa.ubuntu.com/qatracker | notice panel]]. Please ask on #ubuntu-release if you have questions.

=== Milestone Releases ===

Once a Milestone release passes the QA testing, it becomes a Milestone Release and is listed on the [[http://cdimage.ubuntu.com/lubuntu/releases/ | Releases]] as such.

If you would to know more about how this all works, have a read of [[https://wiki.ubuntu.com/QATeam/Overview/TheStages | Stages of testing]].


== General Testing ==
During the release cycle, things will get broken. You can really reduce these occurrences by taking the time to read [[http://ubuntuforums.org/showthread.php?t=1479146|Partial Upgrades]].

=== Known Issues ===
All the known issues for a particular release are mentioned in the Announcement email, and are available to see at [[http://iso.qa.ubuntu.com/ | ISO Tracker]].

=== Manual test of ISO and CD ===
On the help-pages of Ubuntu there is an extensive guide on [[https://help.ubuntu.com/community/HowToMD5SUM|how to MD5SUM]]. In our case the terminal would be [[https://wiki.ubuntu.com/Lubuntu/DocumentationHelp/LXTerminal| LXTerminal]].

 
== Specific Testing ==

=== QA tests ===
You can do more specific tests, like ones done for the Ubuntu ISO : http://iso.qa.ubuntu.com/qatracker

=== Laptop Testing ===

Laptops never cease to have their little 'quirks'. You can help on this important area by heading over to [[https://wiki.ubuntu.com/Testing/Laptop/Procedures | Laptop Testing]] for full details.


=== Unwanted packages ===
Some packages can be automatically installed, but are not wanted on a default installation. To find the package which automatically installed the package that you don't want :
 * Install apt-rdepends
 * run "apt-rdepends -r --show=Depends the_unwanted_package" => It will show which packages depend on the_unwanted_package.
 * run "apt-rdepends -r --show=Recommends the_unwanted_package" => It will show which packages recommend the_package_unwanted (Recommended packages are installed by default).
 * You may have to run the commands several times to see the complete chain of depends / recommends.		 = See Also =
<<BR>>
||<tablestyle="width: 90%; margin: 5px 0;" style="border: none; border-radius: 10px; background-color: #b9defa; font-size: 0.90em;" :> '''Please head over [[https://wiki.ubuntu.com/UbuntuGNOME/Testing/Activities | Testing Activities Page]] for more information about Testing''' ||
<<BR>>


We are now testing Ubuntu GNOME Trusty Tahr Daily Builds



Testing Ubuntu GNOME

"Testing is an infinite process of comparing the invisible to the ambiguous in order to avoid the unthinkable happening to the anonymous." - James Bach


This section is dedicated to the current development version of Ubuntu GNOME. As with all Alphas and Betas they are not suitable for a production environment, please take the time to read Common Questions for Testing

Before Getting Started

Testing and using Development Releases of Ubuntu GNOME (or any other flavor of Ubuntu) isn't meant to be for production machines of daily usage. Testing is to make sure the Stable Release is working as good as possible. Find Bugs, Improve Performance, etc - this is what we do until we finalize the testing process and release a stable version. Whenever you are testing, keep in mind few notes:

  1. Make sure to Backup your important data. If you are using Linux, the best and easier way is to make a copy of your /home folder or partition. If you want to do a full system backup, please see this link and this link too.

  2. You can use Virtual Machines - for example See this. You can use USB Drives or External HDD. You can use your machine. That is totally up to you but please, refer to #1 Smile :)

  3. Using a Development Release is not suitable for daily production machine.
  4. The more you break your installation, the better. That is why, to play it safe, better to use Virtual Machines, Spare Testing Machines and/or USB Drives, specially with Alpha 1 and Alpha 2. Beta Releases are a bit more stable but still under heavy development.

  5. The most important part of testing is to actually install the system and check how the installation process will work. This is very important. Also, if you have say Alpha 1 installed, it is less helpful to just upgrade it to Alpha 2 or Beta 1. Please, do a fresh new install - you can either zsync your ISO or download again.

  6. Finally, always remember: Better Safe Than Sorry Smile :)

Start Testing

Ubuntu GNOME Trusty Tahr Alpha 2 is coming soon!

▶ Please help us to test: Ubuntu GNOME Trusty Tahr Daily Build

Getting Involved

Join Ubuntu GNOME QA Sub-Team

More information on Getting Involved Page

I am NEW to Testing, How Can I help?

Congratulation, you are the best and perfect candidate who actually can help us testing a development release. If you are new to all this, please read this page. If you have any question, join the mailing list and just ask Smile :)

Ubuntu GNOME QA Mailing List

Once you join Ubuntu GNOME QA Sub-Team, automatically, you will be subscribed to the mailing list of Ubuntu GNOME QA Team and this is the address: ubuntugnome-qa@lists.launchpad.net

Share Your Findings or Ask Qs

It is VERY important to share your findings with the team. Also, you can ask anything on the mailing list as well. So, it is a must-do step Smile :)

Bugs

Testing FAQs

Please head over QA/Testing FAQs

See Also


Please head over Testing Activities Page for more information about Testing


UbuntuGNOME/Testing (last edited 2016-11-16 18:29:19 by awjinahn)