Difference between revisions of "Contribute/Bugsquad/BugDays/Beta46Week2"

Jump to: navigation, search
(Created page with 'Placeholder for beta triage week 2.')
 
(add more context based on the previous announcement)
Line 1: Line 1:
Placeholder for beta triage week 2.
+
The 4.6-beta1 BugWeek will be from 11.12 till 17.12 :)
 +
 
 +
{{note|Additions to this wikipage welcome :)}}
 +
 
 +
==Introduction==
 +
 
 +
===Goals of this Week===
 +
This bugweek tries to improve the quality of the 4.6 release by triaging all recent bug reports (bugs from 4.6-beta1 and the pre-beta versions). We also check if the bugs for 4.5 apply for 4.6 and triage those.
 +
 
 +
===Prerequisites===
 +
You should have a recent version of KDE, preferably trunk or the beta 1 release. You can still help if you only have the 4.5.3 release though.
 +
 
 +
====LiveCD====
 +
Some packagers provide LiveCD/DVDs to faciliate testing:
 +
* KDE Four Live (openSUSE) - http://home.kde.org/~kdelive
 +
* openSUSE's KDE repository - http://download.opensuse.org/repositories/KDE:/Medias/images/iso/
 +
* Fedora [http://fedoraproject.org/wiki/Rawhide Rawhide], [http://alt.fedoraproject.org/pub/alt/nightly-composes/kde/ nightly live image]
 +
 
 +
====Packages====
 +
For some distributions pre-compiled and -packaged versions of trunk or the beta are available in additional repositories, ready for consumption:
 +
* '''Gentoo''' (KDE overlay) - [http://kde.gentoo.org/kde4-guide.xml#snapshots Gentoo KDE Guide]
 +
* '''OpenSUSE''' packages [http://en.opensuse.org/Portal:KDE are available]  for openSUSE 11.3 ([http://download.opensuse.org/repositories/KDE:/Distro:/Factory/openSUSE_11.3/KDE4-BASIS.ymp one-click install]), for openSUSE 11.2 ([http://download.opensuse.org/repositories/KDE:/Distro:/Factory/openSUSE_11.2/KDE4-BASIS.ymp one-click install]), and openSUSE Factory ([http://download.opensuse.org/repositories/KDE:/Distro:/Factory/openSUSE_Factory/KDE4-BASIS.ymp one-click install]).
 +
* '''Archlinux''' [https://wiki.archlinux.org/index.php/DeveloperWiki:KDE#Using_the_kde-unstable_repository 4.6 beta]
 +
* '''Fedora'''  [http://fedoraproject.org/wiki/Rawhide Rawhide] already includes 4.6beta, Fedora 14 packages are available in the kde-unstable repository hosted by the [http://kde-redhat.sourceforge.net kde-redhat project].
 +
 
 +
====Sources====
 +
If there are no packages for your distribution, you can always build KDE. [http://techbase.kde.org/Getting_Started/Build/kdesrc-build#Download_and_install_kdesrc-build kdesrc-build] is a nice way to get the newest code and have it compiled for you. Be sure to get the [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/kdesrc-buildrc-sample sample rc from trunk].
 +
 
 +
===Is it a big bug?===
 +
Prioritizing is good. If a major application doesn't work, this should be taken care of.
 +
 
 +
===Keep this page updated!===
 +
After adding triaged bugs on this page, you should keep an eye on their bugzilla status. Add yourself on the CC field in bugzilla to be informed about updates. When a bug is closed on bugzilla, it should be updated on this page.
 +
 
 +
You can do this with the tag <s>...</s>
 +
 
 +
==Sign-in==
 +
Tell developers what you are testing with. (If you expect to upgrade between now and BugDay, put what version you are using now next to the bugs/comments that you put on this page.)
 +
 
 +
Please give distro/version or SVN branch/trunk with revision below (or just beta1 if you're using that). It would be helpful to add what distribution you use.
 +
{|
 +
|-
 +
!IRC Nickname !! KDE version used for testing !! Distribution
 +
|-
 +
|}
 +
 
 +
==Details==
 +
 
 +
Please select a batch of bugs from the [[#Division_of_Labour|Division of Labour]] section below and mark your name next to it and mark it with your irc nickname to show that you are working on it. When you have completed all the bugs in that section, please mark it as complete.
 +
 
 +
For each bug, try and reproduce it as described in the report. Then list it in the appropriate section below. '''If you wish to close or mark as duplicate a bug, please list it here even if you have the bugzilla permissions to do so, in order to get a second opinion from another triager. This will help to reduce the number of incorrect actions taken on bugs.'''
 +
 
 +
===Hints===
 +
* Take note of bugs with '''high priority''' and put them in the section titled [[#High_priority_bugs|High priority bugs]].
 +
* If a bug's description is somewhat unclear, try to provide a better step-by-step procedure on how to reproduce it. This will make it easier for developers to find and fix the bug.
 +
* Some bugs will only be reproducible on certain graphics hardware, so for workspace-related bugs also provide the graphics card and driver you are using.
 +
* Some bugs may not be reproducible on every installation of KDE. Thus we use a 4-eyes principle, having at least 2 triagers look at the bugs before we make any changes on the bugs themselves.
 +
* Some more information on how to mark bugs can be found on [http://techbase.kde.org/index.php?title=Contribute/Bugsquad This page].
 +
 
 +
==Division of Labour==
 +
Please choose a batch that is not already taken and then query bugs.kde.org for all bugs in that batch. Please mark you irc nickname in the table below to show which batches bugs you are working on to avoid duplication of effort.
 +
 
 +
{|
 +
|-
 +
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
 +
|-
 +
|}
 +
 
 +
''(total bugs: 0)''
 +
 
 +
== Completed Bugs ==
 +
Below lists the various sections for completed bugs. This aids everyone in double checking each other's work. In addition this allows those of us that don't have bugzilla permissions to list bugs so that the folks with the permissions can follow up.
 +
 
 +
Please note that this is an experimental layout designed to reduce the number of edit conflicts on this page. Each section is its own subpage. The best way to work with this is to enable section editing by going to "My preferences" > "editing" > "Enable section editing via [edit] links". When you click edit you will automatically edit the subpage.
 +
 
 +
{{:Contribute/Bugsquad/BugDays/Beta46Week2/High priority bugs}}
 +
 
 +
{{:Contribute/Bugsquad/BugDays/Beta46Week2/Bugs needing Version Field changed}}
 +
 
 +
{{:Contribute/Bugsquad/BugDays/Beta46Week2/Bugs with step-by-step Instructions}}
 +
 
 +
{{:Contribute/Bugsquad/BugDays/Beta46Week2/Bugs to be marked as RESOLVED}}
 +
 
 +
{{:Contribute/Bugsquad/BugDays/Beta46Week2/Bugs to be marked as DUPLICATE}}
 +
 
 +
{{:Contribute/Bugsquad/BugDays/Beta46Week2/Bugs to be marked as INVALID}}
 +
 
 +
{{:Contribute/Bugsquad/BugDays/Beta46Week2/Bugs to be marked as NEW}}
 +
 
 +
{{:Contribute/Bugsquad/BugDays/Beta46Week2/Bugs needing attention from developers}}
 +
 
 +
{{:Contribute/Bugsquad/BugDays/Beta46Week2/Bugs needing the reporter's feedback}}
 +
 
 +
{{:Contribute/Bugsquad/BugDays/Beta46Week2/Bugs needing users with particular setups}}
 +
 
 +
{{:Contribute/Bugsquad/BugDays/Beta46Week2/Bug reports against performance issues}}
 +
 
 +
{{:Contribute/Bugsquad/BugDays/Beta46Week2/Bugs that you cant do}}
 +
 
 +
{{:Contribute/Bugsquad/BugDays/Beta46Week2/Wishes}}

Revision as of 09:54, 9 December 2010

The 4.6-beta1 BugWeek will be from 11.12 till 17.12 :)

noframe
 
Note
Additions to this wikipage welcome :)

Contents

Introduction

Goals of this Week

This bugweek tries to improve the quality of the 4.6 release by triaging all recent bug reports (bugs from 4.6-beta1 and the pre-beta versions). We also check if the bugs for 4.5 apply for 4.6 and triage those.

Prerequisites

You should have a recent version of KDE, preferably trunk or the beta 1 release. You can still help if you only have the 4.5.3 release though.

LiveCD

Some packagers provide LiveCD/DVDs to faciliate testing:

Packages

For some distributions pre-compiled and -packaged versions of trunk or the beta are available in additional repositories, ready for consumption:

Sources

If there are no packages for your distribution, you can always build KDE. kdesrc-build is a nice way to get the newest code and have it compiled for you. Be sure to get the sample rc from trunk.

Is it a big bug?

Prioritizing is good. If a major application doesn't work, this should be taken care of.

Keep this page updated!

After adding triaged bugs on this page, you should keep an eye on their bugzilla status. Add yourself on the CC field in bugzilla to be informed about updates. When a bug is closed on bugzilla, it should be updated on this page.

You can do this with the tag <s>...</s>

Sign-in

Tell developers what you are testing with. (If you expect to upgrade between now and BugDay, put what version you are using now next to the bugs/comments that you put on this page.)

Please give distro/version or SVN branch/trunk with revision below (or just beta1 if you're using that). It would be helpful to add what distribution you use.

IRC Nickname KDE version used for testing Distribution

Details

Please select a batch of bugs from the Division of Labour section below and mark your name next to it and mark it with your irc nickname to show that you are working on it. When you have completed all the bugs in that section, please mark it as complete.

For each bug, try and reproduce it as described in the report. Then list it in the appropriate section below. If you wish to close or mark as duplicate a bug, please list it here even if you have the bugzilla permissions to do so, in order to get a second opinion from another triager. This will help to reduce the number of incorrect actions taken on bugs.

Hints

  • Take note of bugs with high priority and put them in the section titled High priority bugs.
  • If a bug's description is somewhat unclear, try to provide a better step-by-step procedure on how to reproduce it. This will make it easier for developers to find and fix the bug.
  • Some bugs will only be reproducible on certain graphics hardware, so for workspace-related bugs also provide the graphics card and driver you are using.
  • Some bugs may not be reproducible on every installation of KDE. Thus we use a 4-eyes principle, having at least 2 triagers look at the bugs before we make any changes on the bugs themselves.
  • Some more information on how to mark bugs can be found on This page.

Division of Labour

Please choose a batch that is not already taken and then query bugs.kde.org for all bugs in that batch. Please mark you irc nickname in the table below to show which batches bugs you are working on to avoid duplication of effort.

Batch No of bugs IRC Nickname Status Query

(total bugs: 0)

Completed Bugs

Below lists the various sections for completed bugs. This aids everyone in double checking each other's work. In addition this allows those of us that don't have bugzilla permissions to list bugs so that the folks with the permissions can follow up.

Please note that this is an experimental layout designed to reduce the number of edit conflicts on this page. Each section is its own subpage. The best way to work with this is to enable section editing by going to "My preferences" > "editing" > "Enable section editing via [edit] links". When you click edit you will automatically edit the subpage.

Contribute/Bugsquad/BugDays/Beta46Week2/High priority bugs

Contribute/Bugsquad/BugDays/Beta46Week2/Bugs needing Version Field changed

Contribute/Bugsquad/BugDays/Beta46Week2/Bugs with step-by-step Instructions

Contribute/Bugsquad/BugDays/Beta46Week2/Bugs to be marked as RESOLVED

Contribute/Bugsquad/BugDays/Beta46Week2/Bugs to be marked as DUPLICATE

Contribute/Bugsquad/BugDays/Beta46Week2/Bugs to be marked as INVALID

Contribute/Bugsquad/BugDays/Beta46Week2/Bugs to be marked as NEW

Contribute/Bugsquad/BugDays/Beta46Week2/Bugs needing attention from developers

Contribute/Bugsquad/BugDays/Beta46Week2/Bugs needing the reporter's feedback

Contribute/Bugsquad/BugDays/Beta46Week2/Bugs needing users with particular setups

Contribute/Bugsquad/BugDays/Beta46Week2/Bug reports against performance issues

Contribute/Bugsquad/BugDays/Beta46Week2/Bugs that you cant do

Contribute/Bugsquad/BugDays/Beta46Week2/Wishes


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal