Testing

Differences between revisions 1 and 44 (spanning 43 versions)
Revision 1 as of 2013-07-22 13:35:21
Size: 14
Editor: amjjawad
Comment: Create New Testing Page for Ubuntu GNOME
Revision 44 as of 2014-01-06 22:25:23
Size: 8311
Editor: amjjawad
Comment: Adding a note with the GNOME Upstream Bugs
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''' ||

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

||<tablestyle="float:right; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||
<<BR>>

= Testing Ubuntu GNOME =
||<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>>
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 [[http://ubuntuforums.org/showthread.php?t=1594833 | 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 [[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''' :)

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

##The daily builds for post alpha1 13.10 are now being built on the cron-job. The first set of alterations that will land in 13.10 are now in.

## * 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]].

##The Dailies are now considered as Release Candidates.

== 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]]''' ||

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

=== 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 :)

=== 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 :)

== Bugs ==
||<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]]''' ||

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

||<tablestyle="width: 40%; margin: 5px 0;" style="border: none; border-radius: 10px; background-color: #ffaaaa; font-size: 0.90em;" :> '''Note:''' It is not uncommon for developers to request the Bug reporter to file the Bug upstream where relevant, obviously the actual reporter can usually provide more info, testing etc. That said, upstream Bugs should really only be submitted once an Ubuntu Developer has requested it. <<BR>><<BR>>'''[[https://wiki.ubuntu.com/Bugs/Upstream/GNOME | Upstream GNOME Bugs]]''' ||

== 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]]''' ||

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

= 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

Note: It is not uncommon for developers to request the Bug reporter to file the Bug upstream where relevant, obviously the actual reporter can usually provide more info, testing etc. That said, upstream Bugs should really only be submitted once an Ubuntu Developer has requested it.

Upstream GNOME 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)