KDE TechBase - User contributions [en]

Projects/Knights

2012-03-25T22:06:02Z

Santa: /* Current features status */

[[Image:Knights.png]]

== About Knights ==

TODO

== Protocols/standards ==

TODO

== Current features status ==

Legend
{| class="wikitable" border="1"
|style="background-color: lightgreen" | Works
|It just works.
|-
|style="background-color: lightgreen" | N/A
| It doesn't work but can't be implemented for any reason, like limitation in the protocol specification.
|-
|style="background-color: yellow" |
|It doesn't work but it's possible to support it. The GUI buttons for the corresponding actions are disabled.
|-
|style="background-color: darkorange" |
| The GUI buttons for the given action(s) are enabled in the GUI but they just do nothing.
|-
|style="background-color: red" |
| The GUI buttons for the given action(s) are enabled in the GUI, also when they are pressed they make the program crash or behave very, very, very bad.
|-
|
| Unknown
|-
|}

Status
{| border="1"
!Player1
!Player2
!Pause
!Undo
!Draw
!Adjourn
!Resign
!Abort
|-
|Human
|Human
|style="background-color: yellow" |
|style="background-color: lightgreen" | Works
|style="background-color: yellow" |
|style="background-color: yellow" |
|style="background-color: yellow" |
|style="background-color: yellow" |
|-
|Human
|gnuchess(Xboard)
|
|
|
|
|
|
|-
|Human
|crafty(Xboard)
|
|
|
|
|
|
|-
|Human
|sjeng(Xboard)
|
|
|
|
|
|
|-
|Human
|stockfish(UCI)
|
|
|
|
|
|
|-
|Human
|freechess.org(FICS)
|
|
|
|
|
|
|-
|gnuchess(Xboard)
|sjeng(Xboard)
|
|
|
|
|
|
|-
|gnuchess(Xboard)
|stockfish(UCI)
|
|
|
|
|
|
|-
|gnuchess(Xboard)
|freechess.org(FICS)
|
|
|
|
|
|
|-
|stockfish(UCI)
|freechess.org(FICS)
|
|
|
|
|
|
|}

Projects/Knights

2012-03-25T21:46:02Z

Santa: /* Current features status */

[[Image:Knights.png]]

== About Knights ==

TODO

== Protocols/standards ==

TODO

== Current features status ==

Legend
{| class="wikitable" border="1"
|style="background-color: lightgreen" | Works
|It just works.
|-
|style="background-color: lightgreen" | N/A
| It doesn't work but can't be implemented for any reason, like limitation in the protocol specification.
|-
|style="background-color: yellow" |
|It doesn't work but it's possible to support it. The GUI buttons for the corresponding actions are disabled.
|-
|style="background-color: darkorange" |
| The GUI buttons for the given action(s) are enabled in the GUI but they just do nothing.
|-
|style="background-color: red" |
| The GUI buttons for the given action(s) are enabled in the GUI, also when they are pressed they make the program crash or behave very, very, very bad.
|-
|
| Unknown
|-
|}

Status
{| border="1"
!Player1
!Player2
!Pause
!Undo
!Draw
!Adjourn
!Resign
!Abort
|-
|Human
|Human
|style="background-color: yellow" |
|style="background-color: green" |
|style="background-color: yellow" |
|style="background-color: yellow" |
|style="background-color: yellow" |
|style="background-color: yellow" |
|-
|Human
|gnuchess(Xboard)
|
|
|
|
|
|
|-
|Human
|crafty(Xboard)
|
|
|
|
|
|
|-
|Human
|sjeng(Xboard)
|
|
|
|
|
|
|-
|Human
|stockfish(UCI)
|
|
|
|
|
|
|-
|Human
|freechess.org(FICS)
|
|
|
|
|
|
|-
|gnuchess(Xboard)
|sjeng(Xboard)
|
|
|
|
|
|
|-
|gnuchess(Xboard)
|stockfish(UCI)
|
|
|
|
|
|
|-
|gnuchess(Xboard)
|freechess.org(FICS)
|
|
|
|
|
|
|-
|stockfish(UCI)
|freechess.org(FICS)
|
|
|
|
|
|
|}

Projects/Knights

2012-03-23T14:08:17Z

Santa: /* Current features status */

[[Image:Knights.png]]

== About Knigths ==

TODO

== Protocols/standards ==

TODO

== Current features status ==

Legend
{| class="wikitable" border="1"
|style="background-color: lightgreen" | Works
|It just works.
|-
|style="background-color: lightgreen" | N/A
| It doesn't work but can't be implemented for any reason, like limitation in the protocol specification.
|-
|style="background-color: yellow" |
|It doesn't work but it's possible to support it. The GUI buttons for the corresponding actions are disabled.
|-
|style="background-color: darkorange" |
| The GUI buttons for the given action(s) are enabled in the GUI but they just do nothing.
|-
|style="background-color: red" |
| The GUI buttons for the given action(s) are enabled in the GUI, also when they are pressed they make the program crash or behave very, very, very bad.
|-
|
| Unknown
|-
|}

Status
{| border="1"
!Player1
!Player2
!Pause
!Undo
!Draw
!Adjourn
!Resign
!Abort
|-
|Human
|Human
|
|
|
|
|
|
|-
|Human
|gnuchess(Xboard)
|
|
|
|
|
|
|-
|Human
|crafty(Xboard)
|
|
|
|
|
|
|-
|Human
|sjeng(Xboard)
|
|
|
|
|
|
|-
|Human
|stockfish(UCI)
|
|
|
|
|
|
|-
|Human
|freechess.org(FICS)
|
|
|
|
|
|
|-
|gnuchess(Xboard)
|sjeng(Xboard)
|
|
|
|
|
|
|-
|gnuchess(Xboard)
|stockfish(UCI)
|
|
|
|
|
|
|-
|gnuchess(Xboard)
|freechess.org(FICS)
|
|
|
|
|
|
|-
|stockfish(UCI)
|freechess.org(FICS)
|
|
|
|
|
|
|}

Projects/Knights

2012-03-23T13:42:06Z

Santa: Oops, add the adjourn feature.

[[Image:Knights.png]]

== About Knigths ==

TODO

== Protocols/standards ==

TODO

== Current features status ==

Legend
{| border="1"
|style="background-color: lightgreen" | Works
|It just works.
|-
|style="background-color: lightgreen" | N/A
| It doesn't work but can't be implemented for any reason, like limitation in the protocol specification.
|-
|style="background-color: yellow" |
|It doesn't work but it's possible to support it. The GUI buttons for the corresponding actions are disabled.
|-
|style="background-color: darkorange" |
| The GUI buttons for the given action(s) are enabled in the GUI but they just do nothing.
|-
|style="background-color: red" |
| The GUI buttons for the given action(s) are enabled in the GUI, also when they are pressed they make the program crash or behave very, very, very bad.
|-
|
| Unknown
|-
|}

Status
{| border="1"
!Player1
!Player2
!Pause
!Undo
!Draw
!Adjourn
!Resign
!Abort
|-
|Human
|Human
|
|
|
|
|
|
|-
|Human
|gnuchess(Xboard)
|
|
|
|
|
|
|-
|Human
|crafty(Xboard)
|
|
|
|
|
|
|-
|Human
|sjeng(Xboard)
|
|
|
|
|
|
|-
|Human
|stockfish(UCI)
|
|
|
|
|
|
|-
|Human
|freechess.org(FICS)
|
|
|
|
|
|
|-
|gnuchess(Xboard)
|sjeng(Xboard)
|
|
|
|
|
|
|-
|gnuchess(Xboard)
|stockfish(UCI)
|
|
|
|
|
|
|-
|gnuchess(Xboard)
|freechess.org(FICS)
|
|
|
|
|
|
|-
|stockfish(UCI)
|freechess.org(FICS)
|
|
|
|
|
|
|}

Projects/Knights

2012-03-23T13:40:14Z

Santa: Initial draft of the features status page.

[[Image:Knights.png]]

== About Knigths ==

TODO

== Protocols/standards ==

TODO

== Current features status ==

Legend
{| border="1"
|style="background-color: lightgreen" | Works
|It just works.
|-
|style="background-color: lightgreen" | N/A
| It doesn't work but can't be implemented for any reason, like limitation in the protocol specification.
|-
|style="background-color: yellow" |
|It doesn't work but it's possible to support it. The GUI buttons for the corresponding actions are disabled.
|-
|style="background-color: darkorange" |
| The GUI buttons for the given action(s) are enabled in the GUI but they just do nothing.
|-
|style="background-color: red" |
| The GUI buttons for the given action(s) are enabled in the GUI, also when they are pressed they make the program crash or behave very, very, very bad.
|-
|
| Unknown
|-
|}

Status
{| border="1"
!Player1
!Player2
!Pause
!Undo
!Draw
!Resign
!Abort
|-
|Human
|Human
|
|
|
|
|
|-
|Human
|gnuchess(Xboard)
|
|
|
|
|
|-
|Human
|crafty(Xboard)
|
|
|
|
|
|-
|Human
|sjeng(Xboard)
|
|
|
|
|
|-
|Human
|stockfish(UCI)
|
|
|
|
|
|-
|Human
|freechess.org(FICS)
|
|
|
|
|
|-
|gnuchess(Xboard)
|sjeng(Xboard)
|
|
|
|
|
|-
|gnuchess(Xboard)
|stockfish(UCI)
|
|
|
|
|
|-
|gnuchess(Xboard)
|freechess.org(FICS)
|
|
|
|
|
|-
|stockfish(UCI)
|freechess.org(FICS)
|
|
|
|
|
|}

Projects/Knights

2012-03-23T12:52:44Z

Santa: Initial Knights page draft

[[Image:Knights.png]]

== About Knigths ==

TODO

== Protocols/standards ==

TODO

== Current features status ==

TODO

Projects

2012-03-23T12:50:08Z

Santa: /* Programs */

{{Template:I18n/Language Navigation Bar|Projects}}
{{note|KDE TechBase Translators: The Projects part is rather a scratchpad for arbitrary projects. It contains texts like IRC logs and rough ideas. ''It probably does not make sense to translate this''. If, however, you wish some part to be translated please either email kde-www@kde.org or comment on #kde-www.}}

{{note|These pages are intended for providing technical documentation for external users of various KDE Projects. For internal project documentation, such as feature plans and meeting minutes please use http://community.kde.org/.}}

= Infrastructure =

{| style="margin: 1em 2.5% 0 2.5%; padding: 0 5px;" cellpadding="5"
|-
|[[Image:Klogo-official-crystal.svg|noframe|left|40px]] ||
;[[/MovetoGit|KDE migration to git]]
:KDE is moving from svn to git, find progress, todo list, etc. here.
|-
|}

= Organisational =

{| style="margin: 1em 2.5% 0 2.5%; padding: 0 5px;" cellpadding="5"
|-
|[[Image:Klogo-official-crystal.svg|noframe|left|40px]] ||
;[http://www.kde.org/community/getinvolved Get Involved with KDE]
:General information for getting involved with KDE projects. Includes a mentor directory for many projects.
|-
|[[Image:Klogo-official-crystal.svg|noframe|left|40px]] ||
;[[/Release_Team|KDE Release Team]]
:The KDE Release Team.
|-
|[[Image:Klogo-official-crystal.svg|noframe|left|40px]] ||
;[[/Documentation|KDE Documentation Project]]
:Creating and maintaining KDE documentation.
|-
|[[Image:Klogo-official-crystal.svg|noframe|left|40px]] ||
;[[/kde.org|kde.org]]
:Information around the *.kde.org websites.
|-
|[[Image:Klogo-official-crystal.svg|noframe|left|40px]] ||
;[[/Promo|KDE Promotion]]
:Promoting KDE and conference organization.
|-
|[[Image:Action_world.svg|noframe|left|40px]] ||
;[[/Partners|Partner Program]]
:KDE partner program targetting ISVs.
|-
| ||
;[[/Usability | KDE Usability project]]
: The KDE Usability Project is an initiative to apply usability principles and practices to the K Desktop Environment.
|-
| [[Image:Bugweeks ladybug.png|noframe|left|40px]]||
;[[Contribute/Bugsquad|KDE BugSquad]]
:The KDE BugSquad keeps track of incoming bugs in KDE software, and goes through old bugs.
|-
| ||
;[[/Summer_of_Code|Summer of Code Projects]]
:Information on Summer of Code projects and prospects related to KDE
|-
| ||
;[[/English Breakfast Network|KDE Code Quality (EBN)]]
: The English Breakfast Network and associated tools dedicated to KDE Quality, including: KDE API Documentation Validation, User Documentation Validation, Source Code Checking, ...
|-
| ||
;[[/KDE Research|KDE Research]]
: Project and community for everyone who is interested in contributing to (funded) research projects with(in) the KDE community.
|-
|}

= Frameworks =

{| style="margin: 1em 2.5% 0 2.5%; padding: 0 5px;" cellpadding="5"
|-
|[[Image:logo_oxygen.png|noframe|left|40px]] ||
;[[/Oxygen|The Oxygen Project]]
:Artwork for KDE4.
|-
|[[Image:Klogo-official-crystal.svg|noframe|left|40px]] ||
;[[/kdelibs|KDE Core Libraries]]
:For the core developers working on the kdelibs module.
|-
|[[Image:Decibel.png|noframe|left|40px]] ||
;[[/Decibel|Decibel]]
:Decibel - Realtime communications framework
|-
| ||
;[[/KGLEngine2D | KGLEngine2D]]
: KGLEngine2D is a framework designed to greatly simplify the development of reach multimedia applications on KDE enabled platforms.
|-
| ||
;[[/KioFuse|KioFuse]]
: Insert KIO resources (remote, archived or compressed files) into the root filesystem hierarchy.
|-
|[[Image:Nepomuk_logo.png|noframe|left|40px]] ||
;[[/Nepomuk|Nepomuk]]
:Nepomuk Semantic Desktop project - Annotation/Indexing/Search/Linking
|-
|[[Image:Action_filequickprint.svg|noframe|left|40px]] ||
;[[/KDEPrint|KDEPrint]]
:Printing related information for KDE.
|-
|[[Image:knetworkmanager.png|noframe|left|40px]] ||
;[[/Network_Management|Network Management]]
: Development on Solid Networking, KNetworkManager applet and configuration tool.
|-
| ||
;[[/D-Bus-WS|D-Bus Web Service Proxy]]
: Fusion of D-Bus services and web services.
|-
| ||
;[[/Silk | Silk]]
: Project Silk - Deep integration of the web
|-
| ||
;[[/Solid | Solid]]
: Solid - The KDE Hardware Library
|-
| ||
;[[/Kbluetooth | Kbluetooth]]
: Kbluetooth - The KDE Bluetooth Library (deprecated)
|-
| ||
;[[/kdesu|kdesu]]
: Considerations and coordination to make kdesu work well with several backends.
|-
| ||
;[[/Telepathy|Telepathy]]
:Telepathy Realtime Communication Framework - Instant Messaging, VoIP and Collaboration.
|-
| ||
;[[/WebKit|WebKit (webkitkde)]]
: Project which aims to integrate WebKit (QtWebKit) into KDE.
|-
| ||
;[[/Widgets and Classes|Widgets & Classes]]
:Widgets and classes that are not in kdelibs but which you may find useful.
|-
| ||
;[[/KSecretsService|KSecretsService - managing KDE application's secrets]]
:Secrets management infrastructure for KDE applications and a collection of related tools, superseding KWallet.
|-
| ||
;[[/Related|Related Projects]]
: Projects which are related to KDE in any way, as dependencies or build tools.
|-
|}

= Programs =

{| style="margin: 1em 2.5% 0 2.5%; padding: 0 5px;" cellpadding="5"
|-
| [[Image:Aki128.png|noframe|left|40px]]||
;[[/Aki | Aki]]
: Aki - Extensive IRC Client
|-
|||
;[[/Digikam|Digikam]]
:Digikam - Photo Management Software.
|-
| [[Image:Hisc-apps-kget.svg|noframe|left|40px]]||
;[[/KGet|KGet]]
: KGet, a KDE Downloader
|-
| ||
;[[/Gwenview|Gwenview]]
:Gwenview, the image viewer.
|-
|[[Image:K3b.png|noframe|left|40px]] ||
;[[/K3b|K3b]]
:K3B, optical disc writer
|-
| ||
;[[/KDevelop4|KDevelop4]]
:KDevelop4, the KDE IDE.
|-
|[[Image:Knights.png|noframe|left|40px]] ||
;[[/Knights|Knights]]
:A chess program for the KDE Platform.
|-
|[[Image:Kopete.svg|noframe|left|40px]] ||
;[[/Kopete|Kopete]]
:Kopete, the KDE Instant Messaging program.
|-
|[[Image:Marble.png|noframe|left|40px]] ||
;[[/Marble|Marble]]
:Marble Desktop Globe - Can You Feel The Earth Spinning?
|-
| ||
;[[/Okular|Okular]]
:Okular, the unified document viewer.
|-
| ||
;[[/rekonq | rekonq]]
: rekonq - A lightweight Web Browser for KDE based on WebKit
|-
|[[Image:Ktimetracker.png|noframe|left|40px]] ||
;[[KTimeTracker]]
:Time management within the KDE PIM.
|-
| ||
;[[/SystemSettings|System Settings]]
: Development on the System Settings configuration tool.
|-
|[[Image:superkaramba.png|noframe|left|40px]] ||
;[[/SuperKaramba|SuperKaramba]]
:SuperKaramba is a tool that allows you to easily create interactive eye-candy on your KDE desktop.
|-
| ||
;[[/KWin|KWin]]
: The KDE Window Manager.
|-
|}

= Suites =

{| style="margin: 1em 2.5% 0 2.5%; padding: 0 5px;" cellpadding="5"
|-
|[[Image:Action_book2.svg|noframe|left|40px]] ||
;[[/Edu|KDE Education Project]]
:Developing educational software for KDE.
|-
| ||
;[[/extragearReleases|Extragear Releases]]
: A current list of what extragear apps are to be released in sync with the core KDE release schedule.
|-
| ||
;[[/KdeFinance | KDE Finance]]
: KDE Finance is a group of KDE-related financial applications
|-
|[[Image:Kdegameslogo_40.png|noframe|left|40px]] ||
;[[/Games|KDE Games Project]]
:Developing desktop's games for KDE.
|-
|[[Image:Action_pencil.svg|noframe|left|40px]] ||
;[[/KOffice|KOffice]] and [http://wiki.koffice.org KOffice.org]
:Developing an Office suite based on KDE.
|-
|[[Image:Action_pencil.svg|noframe|left|40px]] ||
;[[/Calligra/]] and [http://calligra.org Calligra.org]
:Developing an Office suite for KDE.
|-
|[[Image:Action_mail_generic.svg|noframe|left|40px]] ||
;[[/PIM|KDE PIM Project]]
:KDE Personal Information Management.
|-
|[[Image:Plasma_logo.jpg|noframe|left|40px]] ||
;[[/Plasma|Plasma]]
:Quick and easy creation of widgets. Interactive application launchers, window and task managers, weather checkers; they are all made with plasma.
|-
| ||
;[[/Kdetoys | Kdetoys]]
: The Kdetoys project
|-
|[[Image:kdeutils-logo.svg|noframe|left|40px]] ||
;[[/Utils|KDE Utilities Team]]
:For the developers working on the kdeutils module.
|-
| ||
;[[/Necessitas | Necessitas]]
: Necessitas project
|-
|}

= Platforms =

{| style="margin: 1em 2.5% 0 2.5%; padding: 0 5px;" cellpadding="5"
|-
|[[Image:KDE-Mac.png|noframe|left|40px]] ||
;[[/KDE on Mac OS X|KDE on Mac OS X]]
: KDE libraries and applications on Mac OS X.
|-
|[[Image:Konqi-win.png|38px]] ||
;[[/KDE on Windows|KDE on Windows]]
: KDE libraries and applications on MS Windows.
|-
| ||
;[[/KDE on Solaris|KDE on Solaris]]
: KDE libraries and applications on Sun Microsystems Solaris and OpenSolaris.
|-
| ||
;[[/KDE on FreeBSD|KDE on FreeBSD]]
: KDE libraries and applications on FreeBSD and other BSDs.
|-
| ||
;[[Projects/Mobile|Mobile]]
: Project for porting KDE to the Mobile.
|-
|}

__NOTOC__

File:Knights.png

2012-03-23T12:49:33Z

Santa:

Projects/MoveToGit/UsingSvn2Git

2011-07-02T00:01:05Z

Santa: /* Getting the tools */

{{Template:I18n/Language Navigation Bar|Projects/MoveToGit/UsingSvn2Git}}

This page documents how to go about getting a KDE module ready for the Great Git Migration of 2010.

=== Servers to use for all developers ===

KDE Sysadmin provides 3 servers which are fully setup for writing rules. You can find more information about that on: http://community.kde.org/Sysadmin/DeveloperAccessForRuleWriting.

All registered KDE developers have access to these machines. The rest of this document assumes a setup on your local computer, you are free to set it up on your local computer, but there is no need to. You can use the servers provided by KDE Sysadmin.

=== Getting the tools ===

The necessary tools are hosted at [http://www.gitorious.org/svn2git http://www.gitorious.org/svn2git] and [https://projects.kde.org/projects/playground/sdk/kde-ruleset https://projects.kde.org/projects/playground/sdk/kde-ruleset]. To get started do:

<syntaxhighlight lang="bash">
git clone git://gitorious.org/svn2git/svn2git.git
git clone git://anongit.kde.org/kde-ruleset
</syntaxhighlight>

And then install the libsvn-dev package.

This will get you the source code to build svn2git and the KDE ruleset files as they currently exist. Build the svn2git tool before moving on to the next step.

==== Building svn2git ====
Make sure you have Qt4 installed, then simply issue
<nowiki>qmake && make</nowiki> to build the executable called "svn-all-fast-export"

=== How rulesets work ===
The format for the svn2git rules is pretty simple. First and foremost you
have to declare some repositories:

<pre>
create repository kdelibs
end repository
</pre>

This tells svn2git that it should create a git repository called "kdelibs" that we can later on use to put commits into it.

The rest of the file are rules matching specific paths in Subversion, each rule
specifies what to do with the commits that appeared at the given path. The
possible actions are ignoring them or adding them to a particular branch in a particular repository. '''Note:''' Ignoring is done by simply leaving out the information about the repository and the branch.

As examples are more explanatory, the following rule would put all commits from 123453 to 456789 from the path /trunk/KDE/kdelibs into the master branch of
the kdelibs repository:
<pre>
match /trunk/KDE/kdelibs/
min revision 123453
max revision 456789
repository kdelibs
branch master
end match
</pre>

The min and max revision are useful in cases where the same path in SVN contains
code for different branches. An example would be KDevelop3, where KDevelop 3.3 was shipped with KDE 3.5 until 3.5.7, 3.5.8 contained KDevelop 3.4 and 3.5.9 contained KDevelop 3.5 and all of those kdevelop versions are now under /branches/KDE/3.5/kdevelop.

The two revision parameters are however not mandatory, if they're left out, then all commits that went to the given matching path in SVN are taken over into the specified branch.

To generate tags with git you use a special format for the branch parameter: refs/tags/<tagname>. So to put all commits from /tags/KDE/4.4.0/kdelibs into the v4.4.0 tag in the kdelibs git repository the rule would be like this:

<pre>
match /tags/KDE/4.4.0/kdelibs/
repository kdelibs
branch refs/tags/v4.4.0
end match
</pre>

For more examples see the svn2git/samples/ directory and the rules in the kde-ruleset repository.

The recurse action is a hack to tell svn2git to recurse into a directory it has just copied or that existed because it is of interest. Example: if we are importing kdelibs, it exists in {{path|trunk/KDE/kdelibs}}. At branching, someone did: <syntaxhighlight lang="bash">svn cp $SVNROOT/trunk/KDE $SVNROOT/branches/KDE/4.4</syntaxhighlight>

SVN recorded in that commit that branches/KDE/4.4 was the only path changed.
That means the rule <pre>branches/KDE/[^/]+/kdelibs/</pre> will not match.

We need to tell the tool that something interesting happened inside and it
should recurse. Then it will apply again all rules to the files that exist at
that point, at which point the rules will match.

==== Important Details ====

* All rules matching directories need to end with a '/', else the tool will crash at some point. This is a known bug. The only exception are the rules using the recurse-action.

* All rules matching files need to use the prefix rule.

* Matching rules can use Regular Expressions (according to the QRegExp syntax) in the match line and can use backreferences in the repository, prefix and branch parameters using \n (n=1,2,3,...) to reduce the amount of rules.

* The rules form an ordered list that the tool goes through while matching the changed paths for each commit. So if two rules match the same path and neither of the two has more matching criteria, then the rule that is written further up in the file wins. This is useful to exclude certain commits from the extraction process, if you look at the existing kde ruleset you'll notice that at the top some revisions are ignored.

* Each rule file needs to handle all commits, ie. each file should end with a rule which matches everything and does nothing.

=== Setting up your system ===

You will need ~65GB of disk space to get started, as the process requires a copy of the KDE svn database. There is a script that will download this for you (and which can be used to update it periodically using rsync) in kde-ruleset/bin/startSync.

more stuff goes here ...

=== Step-by-Step on writing rules for a module ===

==== Analyzing Subversion history to write rules ====
First of all you should check whether there are already rules for this module in the kde-ruleset repository. If there are rules already please go down to "Running svn2git"

If there are no rules yet, lets start with the master (aka trunk) branch. The easiest way to find out history with svn is executing:
<pre>svn log -v --stop-on-copy file:///path/to/kde_svn/trunk/KDE/module</pre>

Please note that '/path/to/kde_svn/' is the path to the 65GB you downloaded, and the 'trunk/KDE/module' is the module you want to write rules for, but those two put together is *not* a path that physically exists on your disk. svn log is smart enough to do what you want.

This will give you a history of the given module in trunk, it'll stop on the first commit that copied the code from somewhere else. The verbose output will allow you to see where this copy came from.

Now we have a starting point to write a rule, we want all commits from this path in our module repository in the master branch:
<pre>
match /trunk/KDE/module/
repository module
branch master
end match
</pre>
If the log stops at a commit that copied the module from somewhere, we need to
follow this to also get the history imported from the "old" place the module resided. The same svn command can be used with slightly different path argument:

<pre>svn log -v --stop-on-copy file:///path/to/kde_svn/some/other/path@revision</pre>
The @revision is important as the original path usually doesn't exist anymore. With this we can write the next rule to the rules file and repeat until we've finally reached the point where the code was initially imported into svn (or probably cvs in the old days)

Now we can take care of the branches, this is a bit more involved as there may be multiple branches scattered over the /branches directory in svn. You can use the same commands as before to find out the history of a branch if you know the path. This time however you can stop following the source of copy-operations once you've found a source that you've already matched in a rule. That way your branch will be connected to the branch it originated from (which is often trunk aka master) in git.

A useful help with finding branches is svn ls in combination with the path@revision syntax, that way you can view the content of a particular svn directory as it was in an older revision. With this you can even find branches that are not visible (have been deleted) in the current revision.

The rule for putting commits into a git branch in the final repository is only slightly different (the example is for a core module):
<pre>
match /branches/KDE/4.4/module
repository module
branch 4.4
end match
</pre>

And last are the tags, this works the same as branches and trunk, except for using branch refs/tags/v<tag-version> for the branch parameter.

==== Running svn2git ====
This is the easiest, but most time-consuming part. As example lets say that in our current working directory we have the kde rules repository in kde-ruleset subdir, the svn2git tool in the svn2git subdir and the KDE repository in the kde_svn subdir:
<pre>
svn2git/svn-all-fast-export --identity-map kde-ruleset/account-map --rules kde-ruleset/module kde_svn
</pre>

This will take a few hours usually, but it'll spit out the progress. The tool also writes a logfile to module.log, so in case something goes wrong you can find more details in there.

Once its done you should have a new "module" git repository in your current working directory.

==== Checking for proper history in the new git repository ====
To check the history of the created git repository simply change into the directory and use your favourite git command like ''git log'' to check if all is well.

A '''very easy way to check whether the history was imported properly''' is to use the gitk tool from git. It shows you a graphical representation of the history in the git repository which makes it easy to identify where something is wrong.

The tool should be run with the --all switch so it shows all branches.

You can now scroll through the history to check whether things have been imported correctly.

First and foremost there should be the master branch starting at the top with the most recent commit to trunk/ and ending in the oldest commit that imported the code into KDE's svn or cvs repository.

From the master branch there should be several branches going away for each branch you imported. And eventually also branches that start from another non-master branch.

Things that you should look out for are branches that start "nowhere", that is the first commit in the branch has no parent in another branch or master. This means that svn2git didn't see a commit that created this branch from another using a svn cp command. That can mean that you may have forgotton to add a match rule for some path or that the same path was used for different branches in different revisions. The same applies to tags which have a commit without any parent.

This can usually be fixed by using svn log and svn ls to follow the history of the branch. Eventually you might need to apply the min/max revision paramters.

You'll notice that some tags are looking like this:

<pre>
|
* * <v1.2.3>
| |
* *
| /
*
</pre>

Thats normal for our tags even if a bit ugly. The reason is that often compile-fixes are done in trunk/ after the tag has been created and then the commit has been merged over to the tag.

Another thing however are tags that are named vx.y.z_124321. These are tags that have been deleted and re-created later. You can usually see that in the svn log history, these tags can either be manually deleted after the repository creation using git tag or you can add rules that ignore certain revisions of the tag-path before the one putting the commits into the git repository:

<pre>
match /tags/KDE/3.3.2/kdelibs
min revision 424234
max revision 424236
end match
match /tags/KDE/3.3.2/kdelibs
repository kdelibs
branch refs/tags/3.3.2
end match
</pre>

If you choose to delete them manually please make sure to document this with a textfile or inside the rule file so if someone else does the conversion later again he'll know what manual steps you did.

Also try grepping the output from svn2git for the string '"copy from"' (with the double quotation marks). This will give you a list of revisions/paths that svn2git could not detect the origin of. That is someone did a svn cp/mv and the old path is not in the generated git repository.

Before publishing the newly created git repository make sure to repack it. This can greatly reduce it's size (i.e. Phonon's git repository could be shrunken from 18 MB to 5.2 MB)

==== Pushing the Repository to git.kde.org ====
Request a new project as described in the [http://community.kde.org/Sysadmin/GitFAQ#Requesting_project_migrations_from_KDE_SVN_or_Gitorious.org Git KDE Manual]. Then push the repository into that new git project.

==== How to update the account-map file ====

Currently, account-map file is being generated with 'generateAccountMap'[http://gitorious.org/svn2git/kde-ruleset/blobs/master/bin/generateAccountMap] script which parses kde-common/accounts[http://websvn.kde.org/trunk/kde-common/accounts?view=log] and kde-common/disabled-accounts[http://websvn.kde.org/trunk/kde-common/disabled-accounts?view=log] from SVN.

Once you have your git repository you should check if there are accounts not listed in account-map file (you can use checkMissingAccounts[http://gitorious.org/svn2git/kde-ruleset/blobs/master/bin/checkMissingAccounts]), if that is the case, check if the missing accounts are listed in kde-common/accounts or kde-common/disabled-accounts, if it's not there file a sysadmin bug report[https://bugs.kde.org/enter_sysadmin_request.cgi] to get your missing account included in disabled-accounts. Once you get your missing accounts included in disabled accounts, you could generate the account-map file running 'bin/generateAccountMap', then run svn-all-fast-export again. Do not edit account-map file directly!

=== Troubleshooting ===

==== Recurse action doesn't work with cvs2svn tag commits ====

You may have to deal with a commit done by cvs2svn to create a tag, for example:
<pre>
r386536 | (no author) | 2005-02-05 22:16:00 +0100 (Sat, 05 Feb 2005) | 2 lines
Changed paths:
A /branches/beta_0_7_branch (from /trunk:386535)
D /branches/beta_0_7_branch/art-devel
D /branches/beta_0_7_branch/arts
D /branches/beta_0_7_branch/bugs
D /branches/beta_0_7_branch/devel-home
D /branches/beta_0_7_branch/developer.kde.org
D /branches/beta_0_7_branch/enterprise.kde.org
D /branches/beta_0_7_branch/events.kde.org
D /branches/beta_0_7_branch/foundation
D /branches/beta_0_7_branch/kckde
D /branches/beta_0_7_branch/kde-common
D /branches/beta_0_7_branch/kde-i18n
D /branches/beta_0_7_branch/kde-qt-addon
D /branches/beta_0_7_branch/kde-women.kde.org
D /branches/beta_0_7_branch/kdeaccessibility
D /branches/beta_0_7_branch/kdeaddons
D /branches/beta_0_7_branch/kdeadmin
D /branches/beta_0_7_branch/kdeartwork
D /branches/beta_0_7_branch/kdebase
D /branches/beta_0_7_branch/kdebindings
D /branches/beta_0_7_branch/kdeedu
D /branches/beta_0_7_branch/kdeextragear-1
D /branches/beta_0_7_branch/kdeextragear-2
M /branches/beta_0_7_branch/kdeextragear-3
D /branches/beta_0_7_branch/kdeextragear-3/Makefile.am.in
D /branches/beta_0_7_branch/kdeextragear-3/Makefile.cvs
D /branches/beta_0_7_branch/kdeextragear-3/README
D /branches/beta_0_7_branch/kdeextragear-3/configure.in.bot
D /branches/beta_0_7_branch/kdeextragear-3/configure.in.in
D /branches/beta_0_7_branch/kdeextragear-3/digikam
D /branches/beta_0_7_branch/kdeextragear-3/digikamimageplugins
D /branches/beta_0_7_branch/kdeextragear-3/doc
D /branches/beta_0_7_branch/kdeextragear-3/filelight
D /branches/beta_0_7_branch/kdeextragear-3/kcfgcreator
D /branches/beta_0_7_branch/kdeextragear-3/kconfigeditor
D /branches/beta_0_7_branch/kdeextragear-3/kdebluetooth
D /branches/beta_0_7_branch/kdeextragear-3/kdetv
D /branches/beta_0_7_branch/kdeextragear-3/keurocalc
D /branches/beta_0_7_branch/kdeextragear-3/kiosktool
D /branches/beta_0_7_branch/kdeextragear-3/klicker
D /branches/beta_0_7_branch/kdeextragear-3/kplayer
D /branches/beta_0_7_branch/kdeextragear-3/pwmanager
D /branches/beta_0_7_branch/kdeextragear-libs-1
D /branches/beta_0_7_branch/kdegames
D /branches/beta_0_7_branch/kdegraphics
D /branches/beta_0_7_branch/kdeinstaller
D /branches/beta_0_7_branch/kdejava
D /branches/beta_0_7_branch/kdekiosk
D /branches/beta_0_7_branch/kdelibs
D /branches/beta_0_7_branch/kdemultimedia
D /branches/beta_0_7_branch/kdenetwork
D /branches/beta_0_7_branch/kdenonbeta
D /branches/beta_0_7_branch/kdenox
D /branches/beta_0_7_branch/kdepim
D /branches/beta_0_7_branch/kdeplayground-artwork
D /branches/beta_0_7_branch/kdeplayground-base
D /branches/beta_0_7_branch/kdeplayground-edu
D /branches/beta_0_7_branch/kdeplayground-games
D /branches/beta_0_7_branch/kdeplayground-ioslaves
D /branches/beta_0_7_branch/kdeplayground-multimedia
D /branches/beta_0_7_branch/kdeplayground-network
D /branches/beta_0_7_branch/kdeplayground-pim
D /branches/beta_0_7_branch/kdeplayground-utils
D /branches/beta_0_7_branch/kdereview
D /branches/beta_0_7_branch/kdesdk
D /branches/beta_0_7_branch/kdesecurity
D /branches/beta_0_7_branch/kdesupport
D /branches/beta_0_7_branch/kdetoys
D /branches/beta_0_7_branch/kdeutils
D /branches/beta_0_7_branch/kdevelop
D /branches/beta_0_7_branch/kdewebdev
D /branches/beta_0_7_branch/kdoc
D /branches/beta_0_7_branch/kfte
D /branches/beta_0_7_branch/khtmltests
D /branches/beta_0_7_branch/klyx
D /branches/beta_0_7_branch/kmusic
D /branches/beta_0_7_branch/koffice
D /branches/beta_0_7_branch/kofficetests
D /branches/beta_0_7_branch/konstruct
D /branches/beta_0_7_branch/qt-copy
D /branches/beta_0_7_branch/quanta
D /branches/beta_0_7_branch/sysconfig
D /branches/beta_0_7_branch/valgrind
D /branches/beta_0_7_branch/www

This commit was manufactured by cvs2svn to create branch
'beta_0_7_branch'.
</pre>
If you do this
<pre>
match /branches/beta_0_7_branch/kdeextragear-3/krecipes/
repository krecipes
branch 0.7
end match

match /branches/beta_0_7_branch/
min revision 386536
max revision 386536
action recurse
end match
</pre>
svn-all-fast-export will fail, you'll get an error sayining that '/foo/bar/path' was not found where '/foo/bar/path' is one of the deleted paths in the cvs2svn commit. This is because some paths were deleted in the same commit where you want to do an 'action recurse'. Therefore, to avoid matching the deleted paths you should do an action recurse on each intermediate directory from '/branches/beta_0_7_branch/' to '/branches/beta_0_7_branch/kdeextragear-3/krecipes/' and you should use a final '$' to make sure that the deleted paths will not be considered, thusly:
<pre>
match /branches/beta_0_7_branch/kdeextragear-3/krecipes/
repository krecipes
branch 0.7
end match

match /branches/beta_0_7_branch/kdeextragear-3/$
min revision 386536
max revision 386536
action recurse
end match

match /branches/beta_0_7_branch/$
min revision 386536
max revision 386536
action recurse
end match
</pre>

=== Getting Help ===
If you run into strange things or can't find a rule for something you can reach the KDE Git migration team on IRC: irc.freenode.org, #kde-git or on the [https://mail.kde.org/mailman/listinfo/kde-scm-interest kde-scm-interest mailinglist]

Projects/MoveToGit/UsingSvn2Git

2010-07-29T15:55:53Z

Santa: /* How to update the account-map file */

This page documents how to go about getting a KDE module ready for the Great Git Migration of 2010.

=== Getting the tools ===

The necessary tools are hosted at [http://www.gitorious.org/svn2git http://www.gitorious.org/svn2git]. To get started do:

<code bash>
git clone git://gitorious.org/svn2git/svn2git.git
git clone git://gitorious.org/svn2git/kde-ruleset.git
</code>

And then install the libsvn-dev package.

This will get you the source code to build svn2git and the KDE ruleset files as they currently exist. Build the svn2git tool before moving on to the next step.

==== Building svn2git ====
Make sure you have Qt4 installed, then simply issue
<nowiki>qmake && make</nowiki> to build the executable called "svn-all-fast-export"

=== How rulesets work ===
The format for the svn2git rules is pretty simple. First and foremost you
have to declare some repositories:

<pre>
create repository kdelibs
end repository
</pre>

This tells svn2git that it should create a git repository called "kdelibs" that we can later on use to put commits into it.

The rest of the file are rules matching specific paths in Subversion, each rule
specifies what to do with the commits that appeared at the given path. The
possible actions are ignoring them or adding them to a particular branch in a particular repository. '''Note:''' Ignoring is done by simply leaving out the information about the repository and the branch.

As examples are more explanatory, the following rule would put all commits from 123453 to 456789 from the path /trunk/KDE/kdelibs into the master branch of
the kdelibs repository:
<pre>
match /trunk/KDE/kdelibs/
min revision 123453
max revision 456789
repository kdelibs
branch master
end match
</pre>

The min and max revision are useful in cases where the same path in SVN contains
code for different branches. An example would be KDevelop3, where KDevelop 3.3 was shipped with KDE 3.5 until 3.5.7, 3.5.8 contained KDevelop 3.4 and 3.5.9 contained KDevelop 3.5 and all of those kdevelop versions are now under /branches/KDE/3.5/kdevelop.

The two revision parameters are however not mandatory, if they're left out, then all commits that went to the given matching path in SVN are taken over into the specified branch.

To generate tags with git you use a special format for the branch parameter: refs/tag/<tagname>. So to put all commits from /tags/KDE/4.4.0/kdelibs into the v4.4.0 tag in the kdelibs git repository the rule would be like this:

<pre>
match /tags/KDE/4.4.0/kdelibs/
repository kdelibs
branch refs/tags/v4.4.0
end match
</pre>

For more examples see the svn2git/samples/ directory and the rules in the kde-ruleset repository.

The recurse action is a hack to tell svn2git to recurse into a directory it
has just copied or that existed because it is of interest. Example: if we are importing kdelibs, it exists in {{path|trunk/KDE/kdelibs}}. At branching, someone did: <code bash>svn cp $SVNROOT/trunk/KDE $SVNROOT/branches/KDE/4.4</code>

SVN recorded in that commit that branches/KDE/4.4 was the only path changed.
That means the rule <pre>branches/KDE/[^/]+/kdelibs/</pre> will not match.

We need to tell the tool that something interesting happened inside and it
should recurse. Then it will apply again all rules to the files that exist at
that point, at which point the rules will match.

==== Important Details ====

* All matching rules need to end with a '/', else the tool will crash at some point. This is a known bug. The only exception are the rules using the recurse-action.

* Matching rules can use Regular Expressions (according to the QRegExp syntax) in the match line and can use backreferences in the repository and branch parameters using \n (n=1,2,3,...) to reduce the amount of rules.

* The rules form an ordered list that the tool goes through while matching the changed paths for each commit. So if two rules match the same path and neither of the two has more matching criteria, then the rule that is written further up in the file wins. This is useful to exclude certain commits from the extraction process, if you look at the existing kde ruleset you'll notice that at the top some revisions are ignored.

=== Setting up your system ===

You will need ~60GB (is that correct?) of disk space to get started, as the process requires a copy of the KDE svn database. There is a script that will download this for you (and which can be used to update it periodically using rsync) in kde-ruleset/bin/startSync. By default the startSync script runs rsync in "dry run" mode, so before using it to actually get the svn database edit the startSync script and remove the -n from both rsync lines.

more stuff goes here ...

=== Step-by-Step on writing rules for a module ===

==== Analyzing Subversion history to write rules ====
First of all you should check wether there are already rules for this module in the kde-ruleset repository. If there are rules already please go down to "Running svn2git"

If there are no rules yet, lets start with the master (aka trunk) branch. The easiest way to find out history with svn is executing:
<pre>svn log -v --stop-on-copy file:///path/to/kde_svn/trunk/KDE/module</pre>

This will give you a history of the given module in trunk, it'll stop on the first commit that copied the code from somewhere else. The verbose output will allow you to see where this copy came from.

Now we have a starting point to write a rule, we want all commits from this path in our module repository in the master branch:
<pre>
match /trunk/KDE/module/
repository module
branch master
end match
</pre>
If the log stops at a commit that copied the module from somewhere, we need to
follow this to also get the history imported from the "old" place the module resided. The same svn command can be used with slightly different path argument:

<pre>svn log -v --stop-on-copy file:///path/to/kde_svn/some/other/path@revision</pre>
The @revision is important as the original path usually doesn't exist anymore. With this we can write the next rule to the rules file and repeat until we've finally reached the point where the code was initially imported into svn (or probably cvs in the old days)

Now we can take care of the branches, this is a bit more involved as there may be multiple branches scattered over the /branches directory in svn. You can use the same commands as before to find out the history of a branch if you know the path. This time however you can stop following the source of copy-operations once you've found a source that you've already matched in a rule. That way your branch will be connected to the branch it originated from (which is often trunk aka master) in git.

A useful help with finding branches is svn ls in combination with the path@revision syntax, that way you can view the content of a particular svn directory as it was in an older revision. With this you can even find branches that are not visible (have been deleted) in the current revision.

The rule for putting commits into a git branch in the final repository is only slightly different (the example is for a core module):
<pre>
match /branches/KDE/4.4/module
repository module
branch 4.4
end match
</pre>

And last are the tags, this works the same as branches and trunk, except for using branch refs/tags/v<tag-version> for the branch parameter.

==== Running svn2git ====
This is the easiest, but most time-consuming part. As example lets say that in our current working directory we have the kde rules repository in kde-ruleset subdir, the svn2git tool in the svn2git subdir and the KDE repository in the kde_svn subdir:
<pre>
svn2git/svn-all-fast-export --identity-map kde-ruleset/account-map --rules kde-ruleset/module kde_svn
</pre>

This will take a few hours usually, but it'll spit out the progress. The tool also writes a logfile to module.log, so in case something goes wrong you can find more details in there.

Once its done you should have a new "module" git repository in your current working directory.

==== Checking for proper history in the new git repository ====
A very easy way to check wether the history was imported properly is to use the gitk tool from git. It shows you a graphical representation of the history in the git repository which makes it easy to identify where something is wrong.

The tool should be run with the --all switch so it shows all branches.

You can now scroll through the history to check wether things have been imported correctly.

First and foremost there should be the master branch starting at the top with the most recent commit to trunk/ and ending in the oldest commit that imported the code into KDE's svn or cvs repository.

From the master branch there should be several branches going away for each branch you imported. And eventually also branches that start from another non-master branch.

Things that you should look out for are branches that start "nowhere", that is the first commit in the branch has no parent in another branch or master. This means that svn2git didn't see a commit that created this branch from another using a svn cp command. That can mean that you may have forgotton to add a match rule for some path or that the same path was used for different branches in different revisions. The same applies to tags which have a commit without any parent.

This can usually be fixed by using svn log and svn ls to follow the history of the branch. Eventually you might need to apply the min/max revision paramters.

You'll notice that some tags are looking like this:

<pre>
|
* * <v1.2.3>
| |
* *
| /
*
</pre>

Thats normal for our tags even if a bit ugly. The reason is that often compile-fixes are done in trunk/ after the tag has been created and then the commit has been merged over to the tag.

Another thing however are tags that are named vx.y.z_124321. These are tags that have been deleted and re-created later. You can usually see that in the svn log history, these tags can either be manually deleted after the repository creation using git tag or you can add rules that ignore certain revisions of the tag-path before the one putting the commits into the git repository:

<pre>
match /tags/KDE/3.3.2/kdelibs
min revision 424234
max revision 424236
end match
match /tags/KDE/3.3.2/kdelibs
repository kdelibs
branch refs/tags/3.3.2
end match
</pre>

If you choose to delete them manually please make sure to document this with a textfile or inside the rule file so if someone else does the conversion later again he'll know what manual steps you did.

Before publishing the newly created git repository make sure to repack it. This can greatly reduce it's size (i.e. Phonon's git repository could be shrunken from 18 MB to 5.2 MB)

==== How to update the account-map file ====

Currently, account-map file is being generated with 'generateAccountMap'[http://gitorious.org/svn2git/kde-ruleset/blobs/master/bin/generateAccountMap] script which parses kde-common/accounts[http://websvn.kde.org/trunk/kde-common/accounts?view=log] and kde-common/disabled-accounts[http://websvn.kde.org/trunk/kde-common/disabled-accounts?view=log] from SVN.

Once you have your git repository you should check if there are accounts not listed in account-map file (you can use checkMissingAccounts[http://gitorious.org/svn2git/kde-ruleset/blobs/master/bin/checkMissingAccounts]), if that is the case, check if the missing accounts are listed in kde-common/accounts or kde-common/disabled-accounts, if it's not there file a sysadmin bug report[https://bugs.kde.org/enter_sysadmin_request.cgi] to get your missing account included in disabled-accounts. Once you get your missing accounts included in disabled accounts, you could generate the account-map file running 'bin/generateAccountMap', then run svn-all-fast-export again. Do not edit account-map file directly!

=== Troubleshooting ===

==== Recurse action doesn't work with cvs2svn tag commits ====

You may have to deal with a commit done by cvs2svn to create a tag, for example:
<pre>
r386536 | (no author) | 2005-02-05 22:16:00 +0100 (Sat, 05 Feb 2005) | 2 lines
Changed paths:
A /branches/beta_0_7_branch (from /trunk:386535)
D /branches/beta_0_7_branch/art-devel
D /branches/beta_0_7_branch/arts
D /branches/beta_0_7_branch/bugs
D /branches/beta_0_7_branch/devel-home
D /branches/beta_0_7_branch/developer.kde.org
D /branches/beta_0_7_branch/enterprise.kde.org
D /branches/beta_0_7_branch/events.kde.org
D /branches/beta_0_7_branch/foundation
D /branches/beta_0_7_branch/kckde
D /branches/beta_0_7_branch/kde-common
D /branches/beta_0_7_branch/kde-i18n
D /branches/beta_0_7_branch/kde-qt-addon
D /branches/beta_0_7_branch/kde-women.kde.org
D /branches/beta_0_7_branch/kdeaccessibility
D /branches/beta_0_7_branch/kdeaddons
D /branches/beta_0_7_branch/kdeadmin
D /branches/beta_0_7_branch/kdeartwork
D /branches/beta_0_7_branch/kdebase
D /branches/beta_0_7_branch/kdebindings
D /branches/beta_0_7_branch/kdeedu
D /branches/beta_0_7_branch/kdeextragear-1
D /branches/beta_0_7_branch/kdeextragear-2
M /branches/beta_0_7_branch/kdeextragear-3
D /branches/beta_0_7_branch/kdeextragear-3/Makefile.am.in
D /branches/beta_0_7_branch/kdeextragear-3/Makefile.cvs
D /branches/beta_0_7_branch/kdeextragear-3/README
D /branches/beta_0_7_branch/kdeextragear-3/configure.in.bot
D /branches/beta_0_7_branch/kdeextragear-3/configure.in.in
D /branches/beta_0_7_branch/kdeextragear-3/digikam
D /branches/beta_0_7_branch/kdeextragear-3/digikamimageplugins
D /branches/beta_0_7_branch/kdeextragear-3/doc
D /branches/beta_0_7_branch/kdeextragear-3/filelight
D /branches/beta_0_7_branch/kdeextragear-3/kcfgcreator
D /branches/beta_0_7_branch/kdeextragear-3/kconfigeditor
D /branches/beta_0_7_branch/kdeextragear-3/kdebluetooth
D /branches/beta_0_7_branch/kdeextragear-3/kdetv
D /branches/beta_0_7_branch/kdeextragear-3/keurocalc
D /branches/beta_0_7_branch/kdeextragear-3/kiosktool
D /branches/beta_0_7_branch/kdeextragear-3/klicker
D /branches/beta_0_7_branch/kdeextragear-3/kplayer
D /branches/beta_0_7_branch/kdeextragear-3/pwmanager
D /branches/beta_0_7_branch/kdeextragear-libs-1
D /branches/beta_0_7_branch/kdegames
D /branches/beta_0_7_branch/kdegraphics
D /branches/beta_0_7_branch/kdeinstaller
D /branches/beta_0_7_branch/kdejava
D /branches/beta_0_7_branch/kdekiosk
D /branches/beta_0_7_branch/kdelibs
D /branches/beta_0_7_branch/kdemultimedia
D /branches/beta_0_7_branch/kdenetwork
D /branches/beta_0_7_branch/kdenonbeta
D /branches/beta_0_7_branch/kdenox
D /branches/beta_0_7_branch/kdepim
D /branches/beta_0_7_branch/kdeplayground-artwork
D /branches/beta_0_7_branch/kdeplayground-base
D /branches/beta_0_7_branch/kdeplayground-edu
D /branches/beta_0_7_branch/kdeplayground-games
D /branches/beta_0_7_branch/kdeplayground-ioslaves
D /branches/beta_0_7_branch/kdeplayground-multimedia
D /branches/beta_0_7_branch/kdeplayground-network
D /branches/beta_0_7_branch/kdeplayground-pim
D /branches/beta_0_7_branch/kdeplayground-utils
D /branches/beta_0_7_branch/kdereview
D /branches/beta_0_7_branch/kdesdk
D /branches/beta_0_7_branch/kdesecurity
D /branches/beta_0_7_branch/kdesupport
D /branches/beta_0_7_branch/kdetoys
D /branches/beta_0_7_branch/kdeutils
D /branches/beta_0_7_branch/kdevelop
D /branches/beta_0_7_branch/kdewebdev
D /branches/beta_0_7_branch/kdoc
D /branches/beta_0_7_branch/kfte
D /branches/beta_0_7_branch/khtmltests
D /branches/beta_0_7_branch/klyx
D /branches/beta_0_7_branch/kmusic
D /branches/beta_0_7_branch/koffice
D /branches/beta_0_7_branch/kofficetests
D /branches/beta_0_7_branch/konstruct
D /branches/beta_0_7_branch/qt-copy
D /branches/beta_0_7_branch/quanta
D /branches/beta_0_7_branch/sysconfig
D /branches/beta_0_7_branch/valgrind
D /branches/beta_0_7_branch/www

This commit was manufactured by cvs2svn to create branch
'beta_0_7_branch'.
</pre>
If you do this
<pre>
match /branches/beta_0_7_branch/kdeextragear-3/krecipes/
repository krecipes
branch 0.7
end match

match /branches/beta_0_7_branch/
min revision 386536
max revision 386536
action recurse
end match
</pre>
svn-all-fast-export will fail, you'll get an error sayining that '/foo/bar/path' was not found where '/foo/bar/path' is one of the deleted paths in the cvs2svn commit. This is because some paths were deleted in the same commit where you want to do an 'action recurse'. Therefore, to avoid matching the deleted paths you should do an action recurse on each intermediate directory from '/branches/beta_0_7_branch/' to '/branches/beta_0_7_branch/kdeextragear-3/krecipes/' and you should use a final '$' to make sure that the deleted paths will not be considered, thusly:
<pre>
match /branches/beta_0_7_branch/kdeextragear-3/krecipes/
repository krecipes
branch 0.7
end match

match /branches/beta_0_7_branch/kdeextragear-3/$
min revision 386536
max revision 386536
action recurse
end match

match /branches/beta_0_7_branch/$
min revision 386536
max revision 386536
action recurse
end match
</pre>

=== Getting Help ===
If you run into strange things or can't find a rule for something you can reach the KDE Git migration team on IRC: irc.freenode.org, #kde-git or on the [https://mail.kde.org/mailman/listinfo/kde-scm-interest kde-scm-interest mailinglist]

User:Santa

2010-07-28T17:38:30Z

Santa:

I'm a noob who is just getting in touch with KDE programming and community. Thank you for be patient and careful with my job.

At the moment I'm working on krecipes[http://krecipes.sourceforge.net/] and some Debian packages[http://qa.debian.org/developer.php?login=panfaust@gmail.com].

If you can't find me in #kde-devel, #kde-bugs or #krecipes don't hesitate to mail me:
panfaust (at) gmail.com

Projects/MoveToGit/UsingSvn2Git

2010-07-28T17:21:44Z

Santa: Add 'How to update the account-map file'

This page documents how to go about getting a KDE module ready for the Great Git Migration of 2010.

=== Getting the tools ===

The necessary tools are hosted at [http://www.gitorious.org/svn2git http://www.gitorious.org/svn2git]. To get started do:

<code bash>
git clone git://gitorious.org/svn2git/svn2git.git
git clone git://gitorious.org/svn2git/kde-ruleset.git
</code>

And then install the libsvn-dev package.

This will get you the source code to build svn2git and the KDE ruleset files as they currently exist. Build the svn2git tool before moving on to the next step.

==== Building svn2git ====
Make sure you have Qt4 installed, then simply issue
<nowiki>qmake && make</nowiki> to build the executable called "svn-all-fast-export"

=== How rulesets work ===
The format for the svn2git rules is pretty simple. First and foremost you
have to declare some repositories:

<pre>
create repository kdelibs
end repository
</pre>

This tells svn2git that it should create a git repository called "kdelibs" that we can later on use to put commits into it.

The rest of the file are rules matching specific paths in Subversion, each rule
specifies what to do with the commits that appeared at the given path. The
possible actions are ignoring them or adding them to a particular branch in a particular repository. '''Note:''' Ignoring is done by simply leaving out the information about the repository and the branch.

As examples are more explanatory, the following rule would put all commits from 123453 to 456789 from the path /trunk/KDE/kdelibs into the master branch of
the kdelibs repository:
<pre>
match /trunk/KDE/kdelibs/
min revision 123453
max revision 456789
repository kdelibs
branch master
end match
</pre>

The min and max revision are useful in cases where the same path in SVN contains
code for different branches. An example would be KDevelop3, where KDevelop 3.3 was shipped with KDE 3.5 until 3.5.7, 3.5.8 contained KDevelop 3.4 and 3.5.9 contained KDevelop 3.5 and all of those kdevelop versions are now under /branches/KDE/3.5/kdevelop.

The two revision parameters are however not mandatory, if they're left out, then all commits that went to the given matching path in SVN are taken over into the specified branch.

To generate tags with git you use a special format for the branch parameter: refs/tag/<tagname>. So to put all commits from /tags/KDE/4.4.0/kdelibs into the v4.4.0 tag in the kdelibs git repository the rule would be like this:

<pre>
match /tags/KDE/4.4.0/kdelibs/
repository kdelibs
branch refs/tags/v4.4.0
end match
</pre>

For more examples see the svn2git/samples/ directory and the rules in the kde-ruleset repository.

The recurse action is a hack to tell svn2git to recurse into a directory it
has just copied or that existed because it is of interest. Example: if we are importing kdelibs, it exists in {{path|trunk/KDE/kdelibs}}. At branching, someone did: <code bash>svn cp $SVNROOT/trunk/KDE $SVNROOT/branches/KDE/4.4</code>

SVN recorded in that commit that branches/KDE/4.4 was the only path changed.
That means the rule <pre>branches/KDE/[^/]+/kdelibs/</pre> will not match.

We need to tell the tool that something interesting happened inside and it
should recurse. Then it will apply again all rules to the files that exist at
that point, at which point the rules will match.

==== Important Details ====

* All matching rules need to end with a '/', else the tool will crash at some point. This is a known bug. The only exception are the rules using the recurse-action.

* Matching rules can use Regular Expressions (according to the QRegExp syntax) in the match line and can use backreferences in the repository and branch parameters using \n (n=1,2,3,...) to reduce the amount of rules.

* The rules form an ordered list that the tool goes through while matching the changed paths for each commit. So if two rules match the same path and neither of the two has more matching criteria, then the rule that is written further up in the file wins. This is useful to exclude certain commits from the extraction process, if you look at the existing kde ruleset you'll notice that at the top some revisions are ignored.

=== Setting up your system ===

You will need ~60GB (is that correct?) of disk space to get started, as the process requires a copy of the KDE svn database. There is a script that will download this for you (and which can be used to update it periodically using rsync) in kde-ruleset/bin/startSync. By default the startSync script runs rsync in "dry run" mode, so before using it to actually get the svn database edit the startSync script and remove the -n from both rsync lines.

more stuff goes here ...

=== Step-by-Step on writing rules for a module ===

==== Analyzing Subversion history to write rules ====
First of all you should check wether there are already rules for this module in the kde-ruleset repository. If there are rules already please go down to "Running svn2git"

If there are no rules yet, lets start with the master (aka trunk) branch. The easiest way to find out history with svn is executing:
<pre>svn log -v --stop-on-copy file:///path/to/kde_svn/trunk/KDE/module</pre>

This will give you a history of the given module in trunk, it'll stop on the first commit that copied the code from somewhere else. The verbose output will allow you to see where this copy came from.

Now we have a starting point to write a rule, we want all commits from this path in our module repository in the master branch:
<pre>
match /trunk/KDE/module/
repository module
branch master
end match
</pre>
If the log stops at a commit that copied the module from somewhere, we need to
follow this to also get the history imported from the "old" place the module resided. The same svn command can be used with slightly different path argument:

<pre>svn log -v --stop-on-copy file:///path/to/kde_svn/some/other/path@revision</pre>
The @revision is important as the original path usually doesn't exist anymore. With this we can write the next rule to the rules file and repeat until we've finally reached the point where the code was initially imported into svn (or probably cvs in the old days)

Now we can take care of the branches, this is a bit more involved as there may be multiple branches scattered over the /branches directory in svn. You can use the same commands as before to find out the history of a branch if you know the path. This time however you can stop following the source of copy-operations once you've found a source that you've already matched in a rule. That way your branch will be connected to the branch it originated from (which is often trunk aka master) in git.

A useful help with finding branches is svn ls in combination with the path@revision syntax, that way you can view the content of a particular svn directory as it was in an older revision. With this you can even find branches that are not visible (have been deleted) in the current revision.

The rule for putting commits into a git branch in the final repository is only slightly different (the example is for a core module):
<pre>
match /branches/KDE/4.4/module
repository module
branch 4.4
end match
</pre>

And last are the tags, this works the same as branches and trunk, except for using branch refs/tags/v<tag-version> for the branch parameter.

==== Running svn2git ====
This is the easiest, but most time-consuming part. As example lets say that in our current working directory we have the kde rules repository in kde-ruleset subdir, the svn2git tool in the svn2git subdir and the KDE repository in the kde_svn subdir:
<pre>
svn2git/svn-all-fast-export --identity-map kde-ruleset/account-map --rules kde-ruleset/module kde_svn
</pre>

This will take a few hours usually, but it'll spit out the progress. The tool also writes a logfile to module.log, so in case something goes wrong you can find more details in there.

Once its done you should have a new "module" git repository in your current working directory.

==== Checking for proper history in the new git repository ====
A very easy way to check wether the history was imported properly is to use the gitk tool from git. It shows you a graphical representation of the history in the git repository which makes it easy to identify where something is wrong.

The tool should be run with the --all switch so it shows all branches.

You can now scroll through the history to check wether things have been imported correctly.

First and foremost there should be the master branch starting at the top with the most recent commit to trunk/ and ending in the oldest commit that imported the code into KDE's svn or cvs repository.

From the master branch there should be several branches going away for each branch you imported. And eventually also branches that start from another non-master branch.

Things that you should look out for are branches that start "nowhere", that is the first commit in the branch has no parent in another branch or master. This means that svn2git didn't see a commit that created this branch from another using a svn cp command. That can mean that you may have forgotton to add a match rule for some path or that the same path was used for different branches in different revisions. The same applies to tags which have a commit without any parent.

This can usually be fixed by using svn log and svn ls to follow the history of the branch. Eventually you might need to apply the min/max revision paramters.

You'll notice that some tags are looking like this:

<pre>
|
* * <v1.2.3>
| |
* *
| /
*
</pre>

Thats normal for our tags even if a bit ugly. The reason is that often compile-fixes are done in trunk/ after the tag has been created and then the commit has been merged over to the tag.

Another thing however are tags that are named vx.y.z_124321. These are tags that have been deleted and re-created later. You can usually see that in the svn log history, these tags can either be manually deleted after the repository creation using git tag or you can add rules that ignore certain revisions of the tag-path before the one putting the commits into the git repository:

<pre>
match /tags/KDE/3.3.2/kdelibs
min revision 424234
max revision 424236
end match
match /tags/KDE/3.3.2/kdelibs
repository kdelibs
branch refs/tags/3.3.2
end match
</pre>

If you choose to delete them manually please make sure to document this with a textfile or inside the rule file so if someone else does the conversion later again he'll know what manual steps you did.

Before publishing the newly created git repository make sure to repack it. This can greatly reduce it's size (i.e. Phonon's git repository could be shrunken from 18 MB to 5.2 MB)

==== How to update the account-map file ====

Currently, account-map file is being generated with 'generateAccountMap'[http://gitorious.org/svn2git/kde-ruleset/blobs/master/bin/generateAccountMap] script which parses kde-common/accounts[http://websvn.kde.org/trunk/kde-common/accounts?view=log] and kde-common/disabled-accounts[http://websvn.kde.org/trunk/kde-common/disabled-accounts?view=log] from SVN.

Once you have your git repository you should check if there are accounts not listed in account-map file, if that is the case, check if the missing accounts are listed in kde-common/accounts or kde-common/disabled-accounts, if it's not there file a sysadmin bug report[https://bugs.kde.org/enter_sysadmin_request.cgi] to get your missing account included in disabled-accounts. Once you get your missing accounts included in disabled accounts, you could generate the account-map file running 'bin/generateAccountMap', then run svn-all-fast-export again. Do not edit account-map file directly!

=== Troubleshooting ===

==== Recurse action doesn't work with cvs2svn tag commits ====

You may have to deal with a commit done by cvs2svn to create a tag, for example:
<pre>
r386536 | (no author) | 2005-02-05 22:16:00 +0100 (Sat, 05 Feb 2005) | 2 lines
Changed paths:
A /branches/beta_0_7_branch (from /trunk:386535)
D /branches/beta_0_7_branch/art-devel
D /branches/beta_0_7_branch/arts
D /branches/beta_0_7_branch/bugs
D /branches/beta_0_7_branch/devel-home
D /branches/beta_0_7_branch/developer.kde.org
D /branches/beta_0_7_branch/enterprise.kde.org
D /branches/beta_0_7_branch/events.kde.org
D /branches/beta_0_7_branch/foundation
D /branches/beta_0_7_branch/kckde
D /branches/beta_0_7_branch/kde-common
D /branches/beta_0_7_branch/kde-i18n
D /branches/beta_0_7_branch/kde-qt-addon
D /branches/beta_0_7_branch/kde-women.kde.org
D /branches/beta_0_7_branch/kdeaccessibility
D /branches/beta_0_7_branch/kdeaddons
D /branches/beta_0_7_branch/kdeadmin
D /branches/beta_0_7_branch/kdeartwork
D /branches/beta_0_7_branch/kdebase
D /branches/beta_0_7_branch/kdebindings
D /branches/beta_0_7_branch/kdeedu
D /branches/beta_0_7_branch/kdeextragear-1
D /branches/beta_0_7_branch/kdeextragear-2
M /branches/beta_0_7_branch/kdeextragear-3
D /branches/beta_0_7_branch/kdeextragear-3/Makefile.am.in
D /branches/beta_0_7_branch/kdeextragear-3/Makefile.cvs
D /branches/beta_0_7_branch/kdeextragear-3/README
D /branches/beta_0_7_branch/kdeextragear-3/configure.in.bot
D /branches/beta_0_7_branch/kdeextragear-3/configure.in.in
D /branches/beta_0_7_branch/kdeextragear-3/digikam
D /branches/beta_0_7_branch/kdeextragear-3/digikamimageplugins
D /branches/beta_0_7_branch/kdeextragear-3/doc
D /branches/beta_0_7_branch/kdeextragear-3/filelight
D /branches/beta_0_7_branch/kdeextragear-3/kcfgcreator
D /branches/beta_0_7_branch/kdeextragear-3/kconfigeditor
D /branches/beta_0_7_branch/kdeextragear-3/kdebluetooth
D /branches/beta_0_7_branch/kdeextragear-3/kdetv
D /branches/beta_0_7_branch/kdeextragear-3/keurocalc
D /branches/beta_0_7_branch/kdeextragear-3/kiosktool
D /branches/beta_0_7_branch/kdeextragear-3/klicker
D /branches/beta_0_7_branch/kdeextragear-3/kplayer
D /branches/beta_0_7_branch/kdeextragear-3/pwmanager
D /branches/beta_0_7_branch/kdeextragear-libs-1
D /branches/beta_0_7_branch/kdegames
D /branches/beta_0_7_branch/kdegraphics
D /branches/beta_0_7_branch/kdeinstaller
D /branches/beta_0_7_branch/kdejava
D /branches/beta_0_7_branch/kdekiosk
D /branches/beta_0_7_branch/kdelibs
D /branches/beta_0_7_branch/kdemultimedia
D /branches/beta_0_7_branch/kdenetwork
D /branches/beta_0_7_branch/kdenonbeta
D /branches/beta_0_7_branch/kdenox
D /branches/beta_0_7_branch/kdepim
D /branches/beta_0_7_branch/kdeplayground-artwork
D /branches/beta_0_7_branch/kdeplayground-base
D /branches/beta_0_7_branch/kdeplayground-edu
D /branches/beta_0_7_branch/kdeplayground-games
D /branches/beta_0_7_branch/kdeplayground-ioslaves
D /branches/beta_0_7_branch/kdeplayground-multimedia
D /branches/beta_0_7_branch/kdeplayground-network
D /branches/beta_0_7_branch/kdeplayground-pim
D /branches/beta_0_7_branch/kdeplayground-utils
D /branches/beta_0_7_branch/kdereview
D /branches/beta_0_7_branch/kdesdk
D /branches/beta_0_7_branch/kdesecurity
D /branches/beta_0_7_branch/kdesupport
D /branches/beta_0_7_branch/kdetoys
D /branches/beta_0_7_branch/kdeutils
D /branches/beta_0_7_branch/kdevelop
D /branches/beta_0_7_branch/kdewebdev
D /branches/beta_0_7_branch/kdoc
D /branches/beta_0_7_branch/kfte
D /branches/beta_0_7_branch/khtmltests
D /branches/beta_0_7_branch/klyx
D /branches/beta_0_7_branch/kmusic
D /branches/beta_0_7_branch/koffice
D /branches/beta_0_7_branch/kofficetests
D /branches/beta_0_7_branch/konstruct
D /branches/beta_0_7_branch/qt-copy
D /branches/beta_0_7_branch/quanta
D /branches/beta_0_7_branch/sysconfig
D /branches/beta_0_7_branch/valgrind
D /branches/beta_0_7_branch/www

This commit was manufactured by cvs2svn to create branch
'beta_0_7_branch'.
</pre>
If you do this
<pre>
match /branches/beta_0_7_branch/kdeextragear-3/krecipes/
repository krecipes
branch 0.7
end match

match /branches/beta_0_7_branch/
min revision 386536
max revision 386536
action recurse
end match
</pre>
svn-all-fast-export will fail, you'll get an error sayining that '/foo/bar/path' was not found where '/foo/bar/path' is one of the deleted paths in the cvs2svn commit. This is because some paths were deleted in the same commit where you want to do an 'action recurse'. Therefore, to avoid matching the deleted paths you should do an action recurse on each intermediate directory from '/branches/beta_0_7_branch/' to '/branches/beta_0_7_branch/kdeextragear-3/krecipes/' and you should use a final '$' to make sure that the deleted paths will not be considered, thusly:
<pre>
match /branches/beta_0_7_branch/kdeextragear-3/krecipes/
repository krecipes
branch 0.7
end match

match /branches/beta_0_7_branch/kdeextragear-3/$
min revision 386536
max revision 386536
action recurse
end match

match /branches/beta_0_7_branch/$
min revision 386536
max revision 386536
action recurse
end match
</pre>

=== Getting Help ===
If you run into strange things or can't find a rule for something you can reach the KDE Git migration team on IRC: irc.freenode.org, #kde-git or on the [https://mail.kde.org/mailman/listinfo/kde-scm-interest kde-scm-interest mailinglist]

Projects/MoveToGit/UsingSvn2Git

2010-07-28T16:38:24Z

Santa: Add instructions to deal with some cvs2svn commits

This page documents how to go about getting a KDE module ready for the Great Git Migration of 2010.

=== Getting the tools ===

The necessary tools are hosted at [http://www.gitorious.org/svn2git http://www.gitorious.org/svn2git]. To get started do:

<code bash>
git clone git://gitorious.org/svn2git/svn2git.git
git clone git://gitorious.org/svn2git/kde-ruleset.git
</code>

And then install the libsvn-dev package.

This will get you the source code to build svn2git and the KDE ruleset files as they currently exist. Build the svn2git tool before moving on to the next step.

==== Building svn2git ====
Make sure you have Qt4 installed, then simply issue
<nowiki>qmake && make</nowiki> to build the executable called "svn-all-fast-export"

=== How rulesets work ===
The format for the svn2git rules is pretty simple. First and foremost you
have to declare some repositories:

<pre>
create repository kdelibs
end repository
</pre>

This tells svn2git that it should create a git repository called "kdelibs" that we can later on use to put commits into it.

The rest of the file are rules matching specific paths in Subversion, each rule
specifies what to do with the commits that appeared at the given path. The
possible actions are ignoring them or adding them to a particular branch in a particular repository. '''Note:''' Ignoring is done by simply leaving out the information about the repository and the branch.

As examples are more explanatory, the following rule would put all commits from 123453 to 456789 from the path /trunk/KDE/kdelibs into the master branch of
the kdelibs repository:
<pre>
match /trunk/KDE/kdelibs/
min revision 123453
max revision 456789
repository kdelibs
branch master
end match
</pre>

The min and max revision are useful in cases where the same path in SVN contains
code for different branches. An example would be KDevelop3, where KDevelop 3.3 was shipped with KDE 3.5 until 3.5.7, 3.5.8 contained KDevelop 3.4 and 3.5.9 contained KDevelop 3.5 and all of those kdevelop versions are now under /branches/KDE/3.5/kdevelop.

The two revision parameters are however not mandatory, if they're left out, then all commits that went to the given matching path in SVN are taken over into the specified branch.

To generate tags with git you use a special format for the branch parameter: refs/tag/<tagname>. So to put all commits from /tags/KDE/4.4.0/kdelibs into the v4.4.0 tag in the kdelibs git repository the rule would be like this:

<pre>
match /tags/KDE/4.4.0/kdelibs/
repository kdelibs
branch refs/tags/v4.4.0
end match
</pre>

For more examples see the svn2git/samples/ directory and the rules in the kde-ruleset repository.

The recurse action is a hack to tell svn2git to recurse into a directory it
has just copied or that existed because it is of interest. Example: if we are importing kdelibs, it exists in {{path|trunk/KDE/kdelibs}}. At branching, someone did: <code bash>svn cp $SVNROOT/trunk/KDE $SVNROOT/branches/KDE/4.4</code>

SVN recorded in that commit that branches/KDE/4.4 was the only path changed.
That means the rule <pre>branches/KDE/[^/]+/kdelibs/</pre> will not match.

We need to tell the tool that something interesting happened inside and it
should recurse. Then it will apply again all rules to the files that exist at
that point, at which point the rules will match.

==== Important Details ====

* All matching rules need to end with a '/', else the tool will crash at some point. This is a known bug. The only exception are the rules using the recurse-action.

* Matching rules can use Regular Expressions (according to the QRegExp syntax) in the match line and can use backreferences in the repository and branch parameters using \n (n=1,2,3,...) to reduce the amount of rules.

* The rules form an ordered list that the tool goes through while matching the changed paths for each commit. So if two rules match the same path and neither of the two has more matching criteria, then the rule that is written further up in the file wins. This is useful to exclude certain commits from the extraction process, if you look at the existing kde ruleset you'll notice that at the top some revisions are ignored.

=== Setting up your system ===

You will need ~60GB (is that correct?) of disk space to get started, as the process requires a copy of the KDE svn database. There is a script that will download this for you (and which can be used to update it periodically using rsync) in kde-ruleset/bin/startSync. By default the startSync script runs rsync in "dry run" mode, so before using it to actually get the svn database edit the startSync script and remove the -n from both rsync lines.

more stuff goes here ...

=== Step-by-Step on writing rules for a module ===

==== Analyzing Subversion history to write rules ====
First of all you should check wether there are already rules for this module in the kde-ruleset repository. If there are rules already please go down to "Running svn2git"

If there are no rules yet, lets start with the master (aka trunk) branch. The easiest way to find out history with svn is executing:
<pre>svn log -v --stop-on-copy file:///path/to/kde_svn/trunk/KDE/module</pre>

This will give you a history of the given module in trunk, it'll stop on the first commit that copied the code from somewhere else. The verbose output will allow you to see where this copy came from.

Now we have a starting point to write a rule, we want all commits from this path in our module repository in the master branch:
<pre>
match /trunk/KDE/module/
repository module
branch master
end match
</pre>
If the log stops at a commit that copied the module from somewhere, we need to
follow this to also get the history imported from the "old" place the module resided. The same svn command can be used with slightly different path argument:

<pre>svn log -v --stop-on-copy file:///path/to/kde_svn/some/other/path@revision</pre>
The @revision is important as the original path usually doesn't exist anymore. With this we can write the next rule to the rules file and repeat until we've finally reached the point where the code was initially imported into svn (or probably cvs in the old days)

Now we can take care of the branches, this is a bit more involved as there may be multiple branches scattered over the /branches directory in svn. You can use the same commands as before to find out the history of a branch if you know the path. This time however you can stop following the source of copy-operations once you've found a source that you've already matched in a rule. That way your branch will be connected to the branch it originated from (which is often trunk aka master) in git.

A useful help with finding branches is svn ls in combination with the path@revision syntax, that way you can view the content of a particular svn directory as it was in an older revision. With this you can even find branches that are not visible (have been deleted) in the current revision.

The rule for putting commits into a git branch in the final repository is only slightly different (the example is for a core module):
<pre>
match /branches/KDE/4.4/module
repository module
branch 4.4
end match
</pre>

And last are the tags, this works the same as branches and trunk, except for using branch refs/tags/v<tag-version> for the branch parameter.

==== Running svn2git ====
This is the easiest, but most time-consuming part. As example lets say that in our current working directory we have the kde rules repository in kde-ruleset subdir, the svn2git tool in the svn2git subdir and the KDE repository in the kde_svn subdir:
<pre>
svn2git/svn-all-fast-export --identity-map kde-ruleset/account-map --rules kde-ruleset/module kde_svn
</pre>

This will take a few hours usually, but it'll spit out the progress. The tool also writes a logfile to module.log, so in case something goes wrong you can find more details in there.

Once its done you should have a new "module" git repository in your current working directory.

==== Checking for proper history in the new git repository ====
A very easy way to check wether the history was imported properly is to use the gitk tool from git. It shows you a graphical representation of the history in the git repository which makes it easy to identify where something is wrong.

The tool should be run with the --all switch so it shows all branches.

You can now scroll through the history to check wether things have been imported correctly.

First and foremost there should be the master branch starting at the top with the most recent commit to trunk/ and ending in the oldest commit that imported the code into KDE's svn or cvs repository.

From the master branch there should be several branches going away for each branch you imported. And eventually also branches that start from another non-master branch.

Things that you should look out for are branches that start "nowhere", that is the first commit in the branch has no parent in another branch or master. This means that svn2git didn't see a commit that created this branch from another using a svn cp command. That can mean that you may have forgotton to add a match rule for some path or that the same path was used for different branches in different revisions. The same applies to tags which have a commit without any parent.

This can usually be fixed by using svn log and svn ls to follow the history of the branch. Eventually you might need to apply the min/max revision paramters.

You'll notice that some tags are looking like this:

<pre>
|
* * <v1.2.3>
| |
* *
| /
*
</pre>

Thats normal for our tags even if a bit ugly. The reason is that often compile-fixes are done in trunk/ after the tag has been created and then the commit has been merged over to the tag.

Another thing however are tags that are named vx.y.z_124321. These are tags that have been deleted and re-created later. You can usually see that in the svn log history, these tags can either be manually deleted after the repository creation using git tag or you can add rules that ignore certain revisions of the tag-path before the one putting the commits into the git repository:

<pre>
match /tags/KDE/3.3.2/kdelibs
min revision 424234
max revision 424236
end match
match /tags/KDE/3.3.2/kdelibs
repository kdelibs
branch refs/tags/3.3.2
end match
</pre>

If you choose to delete them manually please make sure to document this with a textfile or inside the rule file so if someone else does the conversion later again he'll know what manual steps you did.

Before publishing the newly created git repository make sure to repack it. This can greatly reduce it's size (i.e. Phonon's git repository could be shrunken from 18 MB to 5.2 MB)

=== Troubleshooting ===

==== Recurse action doesn't work with cvs2svn tag commits ====

You may have to deal with a commit done by cvs2svn to create a tag, for example:
<pre>
r386536 | (no author) | 2005-02-05 22:16:00 +0100 (Sat, 05 Feb 2005) | 2 lines
Changed paths:
A /branches/beta_0_7_branch (from /trunk:386535)
D /branches/beta_0_7_branch/art-devel
D /branches/beta_0_7_branch/arts
D /branches/beta_0_7_branch/bugs
D /branches/beta_0_7_branch/devel-home
D /branches/beta_0_7_branch/developer.kde.org
D /branches/beta_0_7_branch/enterprise.kde.org
D /branches/beta_0_7_branch/events.kde.org
D /branches/beta_0_7_branch/foundation
D /branches/beta_0_7_branch/kckde
D /branches/beta_0_7_branch/kde-common
D /branches/beta_0_7_branch/kde-i18n
D /branches/beta_0_7_branch/kde-qt-addon
D /branches/beta_0_7_branch/kde-women.kde.org
D /branches/beta_0_7_branch/kdeaccessibility
D /branches/beta_0_7_branch/kdeaddons
D /branches/beta_0_7_branch/kdeadmin
D /branches/beta_0_7_branch/kdeartwork
D /branches/beta_0_7_branch/kdebase
D /branches/beta_0_7_branch/kdebindings
D /branches/beta_0_7_branch/kdeedu
D /branches/beta_0_7_branch/kdeextragear-1
D /branches/beta_0_7_branch/kdeextragear-2
M /branches/beta_0_7_branch/kdeextragear-3
D /branches/beta_0_7_branch/kdeextragear-3/Makefile.am.in
D /branches/beta_0_7_branch/kdeextragear-3/Makefile.cvs
D /branches/beta_0_7_branch/kdeextragear-3/README
D /branches/beta_0_7_branch/kdeextragear-3/configure.in.bot
D /branches/beta_0_7_branch/kdeextragear-3/configure.in.in
D /branches/beta_0_7_branch/kdeextragear-3/digikam
D /branches/beta_0_7_branch/kdeextragear-3/digikamimageplugins
D /branches/beta_0_7_branch/kdeextragear-3/doc
D /branches/beta_0_7_branch/kdeextragear-3/filelight
D /branches/beta_0_7_branch/kdeextragear-3/kcfgcreator
D /branches/beta_0_7_branch/kdeextragear-3/kconfigeditor
D /branches/beta_0_7_branch/kdeextragear-3/kdebluetooth
D /branches/beta_0_7_branch/kdeextragear-3/kdetv
D /branches/beta_0_7_branch/kdeextragear-3/keurocalc
D /branches/beta_0_7_branch/kdeextragear-3/kiosktool
D /branches/beta_0_7_branch/kdeextragear-3/klicker
D /branches/beta_0_7_branch/kdeextragear-3/kplayer
D /branches/beta_0_7_branch/kdeextragear-3/pwmanager
D /branches/beta_0_7_branch/kdeextragear-libs-1
D /branches/beta_0_7_branch/kdegames
D /branches/beta_0_7_branch/kdegraphics
D /branches/beta_0_7_branch/kdeinstaller
D /branches/beta_0_7_branch/kdejava
D /branches/beta_0_7_branch/kdekiosk
D /branches/beta_0_7_branch/kdelibs
D /branches/beta_0_7_branch/kdemultimedia
D /branches/beta_0_7_branch/kdenetwork
D /branches/beta_0_7_branch/kdenonbeta
D /branches/beta_0_7_branch/kdenox
D /branches/beta_0_7_branch/kdepim
D /branches/beta_0_7_branch/kdeplayground-artwork
D /branches/beta_0_7_branch/kdeplayground-base
D /branches/beta_0_7_branch/kdeplayground-edu
D /branches/beta_0_7_branch/kdeplayground-games
D /branches/beta_0_7_branch/kdeplayground-ioslaves
D /branches/beta_0_7_branch/kdeplayground-multimedia
D /branches/beta_0_7_branch/kdeplayground-network
D /branches/beta_0_7_branch/kdeplayground-pim
D /branches/beta_0_7_branch/kdeplayground-utils
D /branches/beta_0_7_branch/kdereview
D /branches/beta_0_7_branch/kdesdk
D /branches/beta_0_7_branch/kdesecurity
D /branches/beta_0_7_branch/kdesupport
D /branches/beta_0_7_branch/kdetoys
D /branches/beta_0_7_branch/kdeutils
D /branches/beta_0_7_branch/kdevelop
D /branches/beta_0_7_branch/kdewebdev
D /branches/beta_0_7_branch/kdoc
D /branches/beta_0_7_branch/kfte
D /branches/beta_0_7_branch/khtmltests
D /branches/beta_0_7_branch/klyx
D /branches/beta_0_7_branch/kmusic
D /branches/beta_0_7_branch/koffice
D /branches/beta_0_7_branch/kofficetests
D /branches/beta_0_7_branch/konstruct
D /branches/beta_0_7_branch/qt-copy
D /branches/beta_0_7_branch/quanta
D /branches/beta_0_7_branch/sysconfig
D /branches/beta_0_7_branch/valgrind
D /branches/beta_0_7_branch/www

This commit was manufactured by cvs2svn to create branch
'beta_0_7_branch'.
</pre>
If you do this
<pre>
match /branches/beta_0_7_branch/kdeextragear-3/krecipes/
repository krecipes
branch 0.7
end match

match /branches/beta_0_7_branch/
min revision 386536
max revision 386536
action recurse
end match
</pre>
svn-all-fast-export will fail, you'll get an error sayining that '/foo/bar/path' was not found where '/foo/bar/path' is one of the deleted paths in the cvs2svn commit. This is because some paths were deleted in the same commit where you want to do an 'action recurse'. Therefore, to avoid matching the deleted paths you should do an action recurse on each intermediate directory from '/branches/beta_0_7_branch/' to '/branches/beta_0_7_branch/kdeextragear-3/krecipes/' and you should use a final '$' to make sure that the deleted paths will not be considered, thusly:
<pre>
match /branches/beta_0_7_branch/kdeextragear-3/krecipes/
repository krecipes
branch 0.7
end match

match /branches/beta_0_7_branch/kdeextragear-3/$
min revision 386536
max revision 386536
action recurse
end match

match /branches/beta_0_7_branch/$
min revision 386536
max revision 386536
action recurse
end match
</pre>

=== Getting Help ===
If you run into strange things or can't find a rule for something you can reach the KDE Git migration team on IRC: irc.freenode.org, #kde-git or on the [https://mail.kde.org/mailman/listinfo/kde-scm-interest kde-scm-interest mailinglist]

Projects/MovetoGit

2010-07-28T15:41:40Z

Santa: Update Krecipes status

This is the page for co-ordinating KDE's move to [http://git-scm.com/ Git].

If you're interested in helping, you should join the [https://mail.kde.org/mailman/listinfo/kde-scm-interest kde-scm-interest@kde.org] mailinglist and [irc://chat.freenode.net/kde-git #kde-git] on freenode.

Meetings are wednesdays, 19:30 UTC, in #kde-git.

=The Plan=

KDE is, eventually, moving to Git. We will be using gitosis + Redmine + reviewboard on our own servers.

In the summer of 2009, [http://gitorious.org/amarok Amarok] moved to Gitorious to test the waters and find problems that would affect KDE.

After it has been decided in Jun 2010 to use our own servers, Amarok and Konversation moved to git.kde.org/projects.kde.org to test the waters and find problems that would affect KDE.

Once those problems have been solved, all of KDE will be able to switch.

==Why?==

Git offers many advantages over svn, including offline commits and much easier to keep a feature branch up-to-date. Many KDE developers are already using git-svn, but this tool has its limitations. We want to have the full power of Git available, and we have people willing to do the work necessary to migrate.

==How?==

When we move, KDE's svn repository will be migrated into several Git repos, all on git.kde.org. Main modules such as kdelibs and kdebase will each become one repository. Projects in extragear will each have their own repository. The projects.kde.org site will have a list (lists?) of all these repositories using the redmine project wiki. Scripts will be provided for downloading, say, all of extragear, so "moving" a project from kdereview to extragear would simply involve editing a file kept online that defined the location of projects.

A few things will stay in subversion - currently websites, translations and manuals. It's possible they could move to Git later, but they won't be part of the mass migration.

All KDE developers will in principle be able to use their existing "svn" accounts. Developers using HTTPS ideally would request their HTTPS SVN account to be converted to SSH as that makes it easiest for the KDE sysadmins, but alternatively they can also just provide a public key. At some point the KDE sysadmins are going to send everybody with a HTTPS SVN account an email with a link to a web app to collect their key (see http://www.omat.nl/2010/06/13/sysamin-update-your-email-address/).

From the times when gitorious.org was the preferred hosting solution, a procedure to move a project from svn to gitorious.org can be found in [[Projects/MoveToGit/StepsToMove|Steps to follow for Moving]].
Many points probably still apply, but have to be updated.

=Blockers=

Tasks that need to get done before we can migrate

==Setup git.kde.org==
{{Progress bar|40}}
'''Owner:''' Eike, Jeff, Sysadmin team

'''Status:''' ''Progressing''

: It [http://lists.kde.org/?l=kde-scm-interest&m=127612957219466&w=2 has been decided] to use gitosis + Redmine + reviewboard on our own servers rather than gitorious.org. Sysadmin team is preparing git.kde.org for this.

==Write / update importing rules for svn2git==
{{Progress bar|5}}
'''Owner:''' see below - volunteers needed!

'''Status:''' ''sho: ???, tumaix:started to read the docs, cryos: getting started [2010-01-06]''

:The importer is on gitorious.org as svn2git we have a set of rules to tell the importer what svn dirs turn into which git repos and those need constant updating whenever a new branch or tag or project is created. Currently the rules are mostly a rough draft, as seen by the large amount of rule-editing that had to be done for Konversation and Amarok. This has not been done for quite some time and so someone should rsync the svn repo run svn2git and fix the rules and importer whenever the import stops.

:This is a very big task, too big for one person; it's probably best to tackle it one module at a time

:To get started on a module, read [[Projects/MoveToGit/UsingSvn2Git|Using Svn2Git]]

:TZander has done the koffice ruleset as of 2009-01-06

:Jpwhiting has finished (more or less) the kdeaccessibility ruleset 2010-01-24.

:aavci has done the k3b ruleset as of 2010-01-27

progress details:
{| border="1"
!repo
!owner
!%
!comments
|-
|SC/kdeaccessibility
|jpwhiting
|99
|"more or less"?
|-
|SC/kdeadmin
|
|0
|
|-
|SC/kdeartwork
|
|0
|
|-
|SC/kdebase
|
|0
|
|-
|SC/kdebindings
|
|0
|
|-
|SC/kdeedu
|cryos?
|?
|update me!
|-
|SC/kdeedu/marble
|jmho
|100
|Contains: trunk with moves (playground->kdereview->kdeedu), regular kde branches/tags and the following other branches: marble-0.4, gsoc-2009 and geodata-nt. Checking done: gitk --all, verify-git-from-svn
|-
|SC/kdeexamples
|
|0
|
|-
|SC/kdegames
|jobermayr
|95
|coolo or mueller do not give me required information for old tags :-(
|-
|SC/kdegraphics
|
|0
|
|-
|SC/kdelibs
|
|0
|
|-
|SC/kdemultimedia
|eean
|0
|
|-
|SC/kdenetwork
| grundleborg
|0
|
|-
|SC/kdepim
|tnyblom
|95
|Needs verification.
|-
|SC/kdepim-runtime
|tnyblom
|95
|Needs verification.
|-
|SC/kdepimlibs
|tnyblom
|95
|Needs verification.
|-
|SC/kdeplasma-addons
|
|0
|
|-
|SC/kdesdk
|
|0
|
|-
|SC/kdetoys
|
|0
|
|-
|SC/kdeutils
|jobermayr
|95
|coolo or mueller do not give me required information for old tags :-(
|-
|SC/kdewebdev
|
|0
|
|-
|extragear/sdk/kdevelop
| apaku
| 95
| trunk and branches complete, need to cleanup tags from cvs days.
|-
|extragear/sdk/kdevplatform
| apaku
| 100
| done, all tags seem fine all branches are there
|-
|extragear/sdk/kdevelop-plugins
| nsams
| 100
| done
|-
|extragear/sdk/quanta
| nsams
| 99
| done
|-
|extragear/utils/krecipes
| santa
| 85
| Branches are done, I'm working on tags.
|-
|extragear/*/*
|
|xx
|expand the *'s later (let's focus on the base modules first)
|-
|kde-common
|mattr
|75
|analyzing import history
|-
|kdesupport
|
|0
|
|-
|koffice
|tzander
|85
|All but tags are done
|-
|promo
|
|0
|
|-
|quality
|
|0
|
|-
|tests
|
|0
|
|}

== Requirements of KDEPIM and KDAB ==

{{Progress bar|90}}
'''Owner:''' Stephen Kelly

'''Status:''' ''Proposed workflow identified. Partially depends on KDE policies regarding branches and merging. Gathering estimates for porting of tooling from svn to git. People unfamiliar with the tool are starting to learn to use it.''

'''Estimated completion date''': End of May.

'''Summary of issues'''

* Clean slate
** The existing backlog of commits which need to be merged or ported to trunk needs to be empty before the change to git so that nothing gets lost. This is a lot of work and will take time. ''Estimate'' 10 calendar weeks.
* Technical difficulties and limitations.
** Up to KDE 3.5 there was one kdepim module. For the KDE4 cycle, this was split into kdepimlibs and kdepim. For the above mentioned merging to be possible, it makes sense for both to be in the same git module. This poses extra difficulty to the svn2git script.

'''Email threads'''

* Mid-January thread on scm-interest: http://thread.gmane.org/gmane.comp.kde.devel.pim/26726
* Early March thread on kde-core-devel (Till email): http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=63970
* Early March thread on kde-core-devel (Till follow-up):
http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=64069

'''Resolved Issues'''

* Branch maintenance workflow '''Resolution: http://thread.gmane.org/gmane.comp.kde.scm-interest/1310'''
** KDAB maintains several branches of legacy versions of KDE for enterprise customer deployments. [http://websvn.kde.org:80/branches/kdepim/enterprise/ Enterprise 3.5] [http://websvn.kde.org:80/branches/kdepim/enterprise4/ Enterprise 4 (based on KDE 4.2)]. The current KDEPIM trunk known as Enterprise 5 and is Akonadi based.
** Periodically (weekly or so), tags are created from the enterprise branches with bugfixes. http://websvn.kde.org:80/tags/kdepim/ Customers can download the tagged versions with the latest updates. Fixes are merged from the Enterprise 3.5 branch, and into trunk (which sometimes involves a lot of work, as the fix must be ported to Akonadi). Additionally, fixes get merged in the other direction. From official KDE modules into the Enterprise branches.
** Some fixes from Enterprise 3.5 should not be merged into Enterprise 4 for reasons such as no longer being reproducible. Some fixes do not get merged for a long time because they require so much work that porting the fix or feature is deffered. There needs to be a list of commits which should never be merged (blocked commits), and commits which should be merged, but have not been merged yet. The tool [[Development/Tools/svnmerge.py|svnmerge]] is used to facilitate this. svnmerge uses svn properties to maintain lists of commits that are blocked and that have already been integrated. See for example the svn-blocked and svn-integrated properties here: http://websvn.kde.org:80/trunk/KDE/kdepim/. The lists of commits available to be merged into the various branches are here: http://www.kdab.com/~thomas/avail/
** There needs to be a way in git to keep track of what commits have been merged, what commits need to be merged, and what commits are blocked. There needs to be a way of merging only specific commits from a branch, but not all, and not blocked commits. Proposed solutions:
*** git cherry-pick allows 'merging' of individual commits, but does not record where the commits came from. Instead it creates a new commit without any reference to where it came from. This alone is unsuitable.
*** branch per fix. This would lead to an explosion of branches which is not a problem in git as all commits are branches. It may make gitk un-navigatable. There would need to be a naming convention such as komo-merge-<fixname> for branches which should be merged. The commands <tt>git checkout 4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout enterprise4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout master && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt>. That could of course be optimized, but gets the point across. If the code has changed so much that the branch is unmergable, but the fix still needs to be in trunk, the system breaks down.
*** Custom git command with flat text files representing the same information as svnmerge, that is lists of blocked and integrated commits. This is most likely to be a workable solution, possibly together with conventional branch naming.
* Internal Tools and external customer tools and workflows
** KDAB is a consumer of KDE software, but also has downstream customers fetching software from where it is developed. That is, KDE SVN. For example packages are created from the tags in tags/kdepim. Some of these downstreams are less close to KDE and depend on current workflows. If KDE SVN is not the place to get those updates anymore, this needs to be communicated to those downstreams, and the tools updated. ''Estimate'' 1 week to port the tools.
*** Internally used tools have been updated and are now being used to access git repos such as dbus.
* Other commitments
** Project deadlines and other commitments prevent the possibility of blocking off time to work on git migration when so many other things need to be done which have milestones separate to KDE cycles. The required work to convert to git can't be prioritized as highly, and so will take more time.
*** Most of the technical work regarding migration of kdepim repos has been completed by community member Torgny Nyblom.
* Tool knowledge
** People who don't currently know how to use git need to get familiar with it so that transitioning will be nearly seamless, and not result in too much development slowdown.
*** Workshops and use of git-svn have been used to bring developers up to speed on how to use git at some level.

=Nice to have before the migration=

==Push log==
{{Progress bar|100}}
'''Owner:''' sysadmin

'''Status:''' finished

It's a push log, similar to a local repository's reflog.

---------------

For every push, log:
- who pushed (not the Unix username, which will be "git")
- which branch heads changed (what from, what to)
- which tags were created
- the state of all other branches and tags

Just use git commit-tree with the empty tree and save everything in the commit
message, one after the other.

-----------

Gitolite includes this functionality inbuilt to itself, although all repositories are logged in the same file - bcooksley

==Script for downloading virtual KDE hierarchies==
{{Progress bar|0}}
'''Owner''':

'''Status:'''

:Let's start over on this.
what we already have: two build scripts for kde; kdesvn-build and build-tool.
what we want: an easy way for people to get large chunks of kde, without thinking about what urls the repos come from or having to look things up.

do kdesvn-build and build-tool satisfy this well enough?
or do we want a computer-readable file listing all the repos too?

btw, scripty has its own list of repos already. it's just in a rather weird bash file.

'''Discussion:'''

As far as I can see, kdesvn-build is able to do it, it should be just a matter of providing a configuration. As I'm not using build-tool, I can't say anything about it. --jmho

'''Links'''
[http://kdesvn-build.kde.org/]
[[Projects/MovetoGit/MassCloneScript]]
[http://rubyforge.org/projects/build-tool/]

==pre-receive hooks==
{{Progress bar|50}}
'''Owner:''' ''volunteers needed!!''

* Line endings and encodings

'''Discussion:'''
this got accidentally marked as done or something, but it's not.

This has now been ported to Git - bcooksley

Note however that it doesn't look for a .gitattributes file yet - patches welcome ( see sysadmin/repo-management on git.kde.org )

'''Notes:'''
> > As for line-endings, be careful because Git is different from Subversion.
>
> different how?

Just ensure that all files are stored as LF only, except if there's a
.gitattributes file saying "-crlf" (i.e., allow it to have CRLF).

==Snapshot to read-only svn==
{{Progress bar|0}}
'''Owner:'''

:It's work, but maybe some people would like it. NEEDED for documentation, in order to get it back into SVN for the translators/scripty/?

'''Discussion'''

:Could be done with a git-svn gateway presumably? -Mike Arthur 19/10/2009 16:04

:if we leave the docbook stuff in svn, we can avoid this a bit longer. --[[User:Chani|Chani]] 23:21, 12 November 2009 (UTC)

==[[Development/Tutorials/Git|Techbase Documentation]]==
'''Owner:''' Chani, greeneg, - ''please help out!''
{{Progress bar|10}}

:At least minimal documentation about how to checkout, how to request a merge needed, other git documentation and links to other git information would be very useful also.

:see the [[Development/Tutorials/Git|Git Tutorial Page]]. help wanted!!

'''Discussion'''

==Setup git mirrors for cloning==
{{Progress bar|0}}
'''Owner:''' No one (help!)
:Re-purpose the anonsvn servers. This item might be a blocker.
'''Discussion'''

==Local pre-commit hooks==
{{Progress bar|0}}
'''Owner:''' argonel

:A set of recommended local hooks that give useful warnings could be nice to have.

'''Discussion'''
...on the other hand, if we get a lot of bikeshedding about what hooks, then it won't be so nice. so I'd put this in the "very optional" pile. --[[User:Chani|Chani]] 19:10, 16 December 2009 (UTC)

=Post-migration Issues=

==Website Branding==
{{Progress bar|2|text=(initial ideas on the table)}}
'''Owner:''' ruphy

:KDE Gitorious should be branded accordingly, and should be reachable from git.kde.org as well as kde.gitorious.org

'''Discussion'''

Is this section still necessary at all? Perhaps some branding has to be done for redmine or cgit, but I don't know. --jmho

=Unscheduled & Open=

==Allow tagging without involving sysadmins==
{{Progress bar|100}}

'''Owner:''' sysadmin

:Gitolite allows sysadmin to permit certain people on certain repos only to manage both branches and tag without needing force push rights.

'''Discussion'''

==Account setup for Gitolite==
{{Progress bar|0}}

'''Owner:''' ''sysadmin''

:Accounts for existing SVN accounts which use SSH for access have been automatically granted access to Gitolite. Those who are still using HTTPS need to file a sysadmin bug to change their SVN account to SSH and will recieve Git access automatically.

==post-update hooks==
{{Progress bar|90}}
'''Owner:''' ''morice'' ''Ian Monroe''

:* License checker

'''Discussion:'''
We have a fairly complete set of post-update hooks now. See [http://gitorious.org/remotehook remotehook]. However, it would be nice to have a system that lives on the Gitorious server and/or requires less manual maintenance. But its certainly workable and no longer a blocker.

=Completed Tasks=

==Get rid of svn:externals==
{{Progress bar|100}}
'''Owner:''' David Faure

'''Status:''' ''???''

:not possible with git, broken by design.

::

'''Discussion'''

Exists, but ignorable:
* kdesupport shared-desktop-ontologies (temporary)
* playground/utils strigi-chemical/test/ctfr
* playground/devtools kdevelop4-extra-plugins/php/parser/generated/kdevelop-pg-qt
* playground/devtools kdevelop4-extra-plugins/python/parser/generated/kdevelop-pg-qt
* playground/devtools kdevelop4-extra-plugins/qmake/parser/generated/kdevelop-pg-qt
* playground/devtools kommander-plugins/database3/admin
* playground/devtools kommander-plugins/database/admin
* playground/devtools kommander-plugins/datetimefuncs/admin
* playground/devtools kommander-plugins/htmlpart/admin
* playground/devtools kommander-plugins/httpform/admin
* playground/devtools kommander-plugins/kparts/admin
* playground/devtools kommander-plugins/qtactionproxy/admin
* playground/devtools kommander-plugins/timewidget/admin
* playground/devtools kommander-plugins/webkit3/admin
* playground/devtools kpackagemaker/admin

==EBN==
{{Progress bar|95}}
'''Owner:''' ''drf''

'''Status:''' ''Amarok has EBN checks''

:EBN's krazy checks currently run on kde's svn repo; it needs upgrading to download and check our git repos too.

:This would be easier if there was a repo-list that EBN could parse, as it can no longer just svn up to get everything.

==Talk to people using other distros about git==
{{Progress bar|100}}
'''Owner:''' Sebas, Eike

'''Discussion'''
* Gentoo: They seem to be prepared for moving their live SVN packages to git; their package manager has easily-reusable classes to fetch from an SCM and moving the ebuilds to using the git class rather than the SVN class should be easy. Positive comments to that end from people in #gentoo-kde.
* Fedora: Some unhappyness about git because SVN allows them to remotely produce a diff between two SVN URLs (or two revisions of one and the same URL) without making a checkout first, while git requires making a clone. Kevin Kofler (IRC nick Kevin_Kofler, #fedora-kde) says this will make their packager work harder.
* Debian: Is indifferent about the SCM switch.

==Post Update hooks==
{{Progress bar|100}}
'''Owner:''' ''morice, johan, mattr

:List of scripts needed:
:* BUG/CCMAIL
:* email/CIA

:Gitorious needs to provide a way for hooks to be called; KDE needs to write said hooks.

'''Discussion'''

:There is a branch of gitorious called web-hooks http://gitorious.org/gitorious/mainline/commits/web-hooks --Panagiotis Papadopoulos 1 November 2009
:Same situation as commit emails. I can do it but it doesn't scale well and a Gitorious-supported solution would be nicer. --[[User:Eean|eean]] 16:07, 12 November 2009 (UTC)

==Reviewboard==
{{Progress bar|100}}
'''Owner:''' darktears

This should be easily done with Gitorious web interface and merge requests actually.

'''Discussion'''

:but reviewboard has features gitorious (right now) doesn't, like commenting on specific lines and not having to set up a merge request. --chani
::Also email notifications when someone reviews are needed --thomasz
:We're working on this for someone else right now, so pretty soon --johan-s
:I consider the latest changes to gitorious to finish this. If more reviewboard features are still needed, and git supports reviewboard, I think this is something we can look at doing post-conversion. --Ian Monroe

==Gitorious Needs a feature to disable merge request emails for certain repos==
{{Progress bar|100}}
'''Owner:''' [http://gitorious.org/gitorious Gitorious]

Have a sensible system for merge request emails. This is now in place - you can join groups, chose whether to have emails on a per repo basis, etc.

==SSH blocked in corporations and universities.==
{{Progress bar|100}}
'''Owner:''' ''Unknown''

:Some universities tend to block the SSH port. There should be a workaround to use SSH on some different port. github.com already runs a SSH server on port 443. But that assumes you are using a proxy. It has been found that this hasn't worked with a lot of people, especially those who have a direct connection to the internet ( so some transparent blocking by the ISP ). It would be great if (almost) every KDE developer were to be asked to check if other ports work before KDE made the switch. Otherwise there could be an automated email where the git patches could be sent, and appropriately patched to the right location too.

'''Discussion'''

:http://blog.gitorious.org/2009/10/20/stuck-behind-a-firewall/, and there's always been HTTP cloning (although the current impl. in Git is a bit on the slow side) --johan-s

==Talk to windows guys about git.==
{{Progress bar|100}}
'''Owner:''' aseigo

'''Discussion'''

They aren't huge fans of git, but are using it. They require a single mainline and can't cope with multiple branches. Otherwise, it's workable, even if it will take an adjustment period.

==pre-commit hooks==
{{Progress bar|100}}
'''Owner:''' ''(unknown)''

:acltest, docbook, EOL/UTF-8

:A web hook isn't good enough for these because they have to run and return whether to allow the push, for every single push to every KDE repo.

'''Discussion'''

:gitorious guys said they *might* be willing to allow a few scripts on their server for KDE as a special exception, iirc. --chani

:: Yes, at least for basic things, heavier things like doc building would probably have to be mirrored (goes for pre/post) --johan-s

:It turns out that acl and docbook might not be needed so long as web and docs/ stuff stays in svn.

:: Here's where to find the current scripts - http://websvn.kde.org/trunk/kde-common/svn/hooks/ --[[User:Argonel|Argonel]] 23:06, 11 November 2009 (UTC)

::So: this is actually done because it needs no longer to be done? (boud)

::Apparently, so; moving to complete. (aseigo)

= other notes =

==kde-common/accounts==

Someone said: KDE accounts file is no longer necessary---used for mapping svn ID -> email, but we have that now from Gitorious.
Answer from David Faure: I strongly disagree. We still need a KDE accounts file. This is very useful for finding people's email addresses, and having an overview on the number of active kde contributors; and if we keep it we can even have a kdepim resource again for filling an addressbook from it, for completion in kmail's composer (so you can write to any other kde contributor by just typing his/her name). It's also used for populating automatically the kde-cvs-announce mailing-list, for announcements. kde-common/accounts is our family tree (well, list), let's not get rid of it.

Here's my proposal for a kde-common/accounts replacement for the git era: We write a post-receive hook that looks at every commit and records all known email addresses for a given real name as well as the commit hash and date of when an address was last encountered. We can then present that data in the form of a file like kde-common/accounts, or write a web interface to query it (with nice links to the commits on Gitorious, etc.) --Eike (Sho_ on IRC)

To clear up possible confusion: The author information for a given commit is baked into the commit object itself, and comes from the configuration of the git repository it was created in. It is unrelated to any Gitorious account. Due to the distributed nature of Git, the one who uses his Gitorious account to push a commit need not be the same who created it. If Developer A creates a commit in his local clone and Developer B fetches it into his local clone directly from Developer A's machine and then pushes it into the public repo, the repo will only show a commit from Developer A. The Gitorious website will show that Developer B has pushed up a commit from Developer A, but that data is not contained in the repository. Thus collecting only Gitorious accounts and their mail addresses is insufficient. --Eike

==Random==
http://mail.kde.org/pipermail/dot-stories/2005-May/000509.html might be a good guide on what docs we need.

some of this stuff was from the list from GCDS that was in this email [http://markmail.org/message/u6eqfjece7fibfyo http://markmail.org/message/u6eqfjece7fibfyo]

==IRC Meetings==
* [[Projects/MovetoGit/Meeting1111|Minutes]] of meeting 11 November 2009
* [[Projects/MovetoGit/Meeting1118|Next meeting]] 18:00, 25 November 2009 (UTC)

= jobs =
''TODO merge this with the todolists above''

michael jansen: talking to kdesvn-build/mpyne
:--Done? -> http://kdesvn-build.kde.org/releases/kdesvn-build-1.10.php -- Panagiotis Papadopoulos 1 November 2009
::Yes, but the __kdesvn-build-remote used in the impl isn't pleasant for users already on git so it still needs more work for them. [[User:Mpyne|Mpyne]] 20:32, 11 November 2009 (UTC)

jonas: domain name

ML: convert to SSH

chani: techbase docs for scripty

sebas/lydia/leo: communication with teams! tell people! keeping track that
everything is being done.

Projects/MovetoGit

2010-04-27T15:45:17Z

Santa: /* Write / update importing rules for svn2git */

This is the page for co-ordinating KDE's move to [http://git-scm.com/ Git].

If you're interested in helping, you should join the [https://mail.kde.org/mailman/listinfo/kde-scm-interest kde-scm-interest@kde.org] mailinglist and [irc://chat.freenode.net/kde-git #kde-git] on freenode.

Meetings are wednesdays, 19:30 UTC, in #kde-git.

=The Plan=

KDE is, eventually, moving to Git. We will be using [http://gitorious.org/ gitorious.org] servers, with funding from Nokia. We will also have our own mirrors using existing KDE servers.

We are working with the Gitorious people to ensure their server will meet all our needs as well as everyone's privacy requirements. The distributed nature of Git will make it easy for us to migrate off gitorious.org at any time should the need arise (but that's unlikely :).

In the summer of 2009, [http://gitorious.org/amarok Amarok] moved to Gitorious to test the waters and find problems that would affect KDE. Once those problems have been solved, all of KDE will be able to switch.

==Why?==

Git offers many advantages over svn, including offline commits and much easier to keep a feature branch up-to-date. Many KDE developers are already using git-svn, but this tool has its limitations. We want to have the full power of Git available, and we have people willing to do the work necessary to migrate.

==How?==

When we move, KDE's svn repository will be migrated into several Git repos, all on gitorious.org. Main modules such as kdelibs and kdebase will each become one repository. Projects in extragear will each have their own repository. The kde.gitorious.org site will have a list (lists?) of all these repositories using the builtin project wiki. Scripts will be provided for downloading, say, all of extragear, so "moving" a project from kdereview to extragear would simply involve editing a file kept online that defined the location of projects.

A few things will stay in subversion - currently websites, translations and manuals. It's possible they could move to Git later, but they won't be part of the mass migration.

On Gitorious, all KDE developers will be part of the [http://gitorious.org/+kde-developers kde-developers group]. Developers in this group are required to set their "full name" for their Gitorious account to their real name. If you want to be in this group, file a bugreport for sysadmin on bugs.kde.org. :)

The procedure to move a project from svn to gitorious.org can be found in [[Projects/MoveToGit/StepsToMove|Steps to follow for Moving]].

=Blockers=

Tasks that need to get done before we can migrate

==SLA for gitorious.org==
{{Progress bar|30}}
'''Owner:''' aseigo, frank

'''Status:''' ''Progressing well; will take a while''

: The SLA terms need to be documented as well as who will be footing the bill, if any. TZander has talked to Shortcut AS and sent the relevant information (eg cost) to the KDE eV board.

: aseigo and Frank (and someone?) had a meeting with Shortcut people during tokamak. They asked for a rather large sum of money; negotiations are continuing, but we might want to consider hosting our own server...

==Write / update importing rules for svn2git==
{{Progress bar|5}}
'''Owner:''' see below - volunteers needed!

'''Status:''' ''sandsmark: stuck on a svn2git bug. sho: ???, tumaix:started to read the docs, cryos: getting started [2010-01-06]''

:The importer is on gitorious.org as svn2git we have a set of rules to tell the importer what svn dirs turn into which git repos and those need constant updating whenever a new branch or tag or project is created. Currently the rules are mostly a rough draft, as seen by the large amount of rule-editing that had to be done for Konversation and Amarok. This has not been done for quite some time and so someone should rsync the svn repo run svn2git and fix the rules and importer whenever the import stops.

:This is a very big task, too big for one person; it's probably best to tackle it one module at a time

:To get started on a module, read [[Projects/MoveToGit/UsingSvn2Git|Using Svn2Git]]

:TZander has done the koffice ruleset as of 2009-01-06

:Jpwhiting has finished (more or less) the kdeaccessibility ruleset 2010-01-24.

:aavci has done the k3b ruleset as of 2010-01-27

progress details:
{| border="1"
!repo
!owner
!%
!comments
|-
|SC/kdeaccessibility
|jpwhiting
|99
|"more or less"?
|-
|SC/kdeadmin
|
|0
|
|-
|SC/kdeartwork
|
|0
|
|-
|SC/kdebase
|
|0
|
|-
|SC/kdebindings
|
|0
|
|-
|SC/kdeedu
|cryos?
|?
|update me!
|-
|SC/kdeexamples
|
|0
|
|-
|SC/kdegames
|tumaix?
|?
|update me!
|-
|SC/kdegraphics
|
|0
|
|-
|SC/kdelibs
|
|0
|
|-
|SC/kdemultimedia
|eean
|0
|
|-
|SC/kdenetwork
| grundleborg
|0
|
|-
|SC/kdepim
|tnyblom
|25
|Basic rules in place, testing and tweaking pending.
|-
|SC/kdepim-runtime
|tnyblom
|25
|Basic rules in place, testing and tweaking pending.
|-
|SC/kdepimlibs
|tnyblom
|90
|Some minor history glitches, but mostly done.
|-
|SC/kdeplasma-addons
|
|0
|
|-
|SC/kdesdk
|
|0
|
|-
|SC/kdetoys
|
|0
|
|-
|SC/kdeutils
|
|0
|
|-
|SC/kdewebdev
|
|0
|
|-
|extragear/sdk/kdevelop
| apaku
| 95
| trunk and branches complete, need to cleanup tags from cvs days.
|-
|extragear/sdk/kdevplatform
| apaku
| 100
| done, all tags seem fine all branches are there
|-
|extragear/sdk/kdevelop-plugins
| nsams
| 100
| done
|-
|extragear/sdk/quanta
| nsams
| 99
| done
|-
|extragear/utils/krecipes
| santa
| 10
|
|-
|extragear/*/*
|
|xx
|expand the *'s later (let's focus on the base modules first)
|-
|kde-common
|mattr
|75
|analyzing import history
|-
|kdesupport
|
|0
|
|-
|koffice
|tzander
|85
|All but tags are done
|-
|promo
|
|0
|
|-
|quality
|
|0
|
|-
|tests
|
|0
|
|}

== Requirements of KDEPIM and KDAB ==

{{Progress bar|70}}
'''Owner:''' Stephen Kelly

'''Status:''' ''Proposed workflow identified. Partially depends on KDE policies regarding branches and merging. Gathering estimates for porting of tooling from svn to git. People unfamiliar with the tool are starting to learn to use it.''

'''Estimated completion date''': End of May.

'''Summary of issues'''

* Clean slate
** The existing backlog of commits which need to be merged or ported to trunk needs to be empty before the change to git so that nothing gets lost. This is a lot of work and will take time. ''Estimate'' 10 calendar weeks.
* Internal Tools and external customer tools and workflows
** KDAB is a consumer of KDE software, but also has downstream customers fetching software from where it is developed. That is, KDE SVN. For example packages are created from the tags in tags/kdepim. Some of these downstreams are less close to KDE and depend on current workflows. If KDE SVN is not the place to get those updates anymore, this needs to be communicated to those downstreams, and the tools updated. ''Estimate'' 1 week to port the tools.
** People who don't currently know how to use git need to get familiar with it so that transitioning will be nearly seamless, and not result in too much development slowdown.
* Other commitments
** Project deadlines and other commitments prevent the possibility of blocking off time to work on git migration when so many other things need to be done which have milestones separate to KDE cycles. The required work to convert to git can't be prioritized as highly, and so will take more time.
* Technical difficulties and limitations.
** Up to KDE 3.5 there was one kdepim module. For the KDE4 cycle, this was split into kdepimlibs and kdepim. For the above mentioned merging to be possible, it makes sense for both to be in the same git module. This poses extra difficulty to the svn2git script.

'''Email threads'''

* Mid-January thread on scm-interest: http://thread.gmane.org/gmane.comp.kde.devel.pim/26726
* Early March thread on kde-core-devel (Till email): http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=63970
* Early March thread on kde-core-devel (Till follow-up):
http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=64069

'''Resolved Issues'''

* Branch maintenance workflow '''Resolution: http://thread.gmane.org/gmane.comp.kde.scm-interest/1310'''
** KDAB maintains several branches of legacy versions of KDE for enterprise customer deployments. [http://websvn.kde.org:80/branches/kdepim/enterprise/ Enterprise 3.5] [http://websvn.kde.org:80/branches/kdepim/enterprise4/ Enterprise 4 (based on KDE 4.2)]. The current KDEPIM trunk known as Enterprise 5 and is Akonadi based.
** Periodically (weekly or so), tags are created from the enterprise branches with bugfixes. http://websvn.kde.org:80/tags/kdepim/ Customers can download the tagged versions with the latest updates. Fixes are merged from the Enterprise 3.5 branch, and into trunk (which sometimes involves a lot of work, as the fix must be ported to Akonadi). Additionally, fixes get merged in the other direction. From official KDE modules into the Enterprise branches.
** Some fixes from Enterprise 3.5 should not be merged into Enterprise 4 for reasons such as no longer being reproducible. Some fixes do not get merged for a long time because they require so much work that porting the fix or feature is deffered. There needs to be a list of commits which should never be merged (blocked commits), and commits which should be merged, but have not been merged yet. The tool [[Development/Tools/svnmerge.py|svnmerge]] is used to facilitate this. svnmerge uses svn properties to maintain lists of commits that are blocked and that have already been integrated. See for example the svn-blocked and svn-integrated properties here: http://websvn.kde.org:80/trunk/KDE/kdepim/. The lists of commits available to be merged into the various branches are here: http://www.kdab.com/~thomas/avail/
** There needs to be a way in git to keep track of what commits have been merged, what commits need to be merged, and what commits are blocked. There needs to be a way of merging only specific commits from a branch, but not all, and not blocked commits. Proposed solutions:
*** git cherry-pick allows 'merging' of individual commits, but does not record where the commits came from. Instead it creates a new commit without any reference to where it came from. This alone is unsuitable.
*** branch per fix. This would lead to an explosion of branches which is not a problem in git as all commits are branches. It may make gitk un-navigatable. There would need to be a naming convention such as komo-merge-<fixname> for branches which should be merged. The commands <tt>git checkout 4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout enterprise4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout master && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt>. That could of course be optimized, but gets the point across. If the code has changed so much that the branch is unmergable, but the fix still needs to be in trunk, the system breaks down.
*** Custom git command with flat text files representing the same information as svnmerge, that is lists of blocked and integrated commits. This is most likely to be a workable solution, possibly together with conventional branch naming.

=Nice to have before the migration=

==Push log==
{{Progress bar|0}}
'''Owner:''' nobody!!

'''Status:''' argonel had a hd failure :( [2010-01-06]

:Gitorious records who pushed each commit. This is useful information because commits themselves can say anything, and there are legitimate reasons to push commits with another person's name.

:Internally, Gitorious stores this information in an SQL database, and the information is viewable through the web interface. However we want a way to backup this information for the case that Gitorious suddenly go offline.

:quotes from the mailing list:

> How about every repo has, by convention, a "commits" branch and
> a post commit hook that ensures whatever meta info is required,
> however it can be gleaned, is also checked into that commits branch.
> A bit like how gitosis uses a repo to store auth/acl info to help
> manage the other repos.

That's exactly my idea. And of course it won't be named commits, because we're
not talking about commits.

It's a push log, similar to a local repository's reflog.

---------------

For every push, log:
- who pushed (not the Unix username, which will be "git")
- which branch heads changed (what from, what to)
- which tags were created
- the state of all other branches and tags

Just use git commit-tree with the empty tree and save everything in the commit
message, one after the other.

-----------

This does not require help from gitorious.org until the script is actually written: it's just another pre-receive hook for them to install on their servers.
it *might* also be possible to run it as a post-receive hook (in which case we can do the whole thing ourselves).

if we self-host, then we won't need this.

==Script for downloading virtual KDE hierarchies==
{{Progress bar|0}}
'''Owner''':

'''Status:'''

:Let's start over on this.
what we already have: two build scripts for kde; kdesvn-build and build-tool.
what we want: an easy way for people to get large chunks of kde, without thinking about what urls the repos come from or having to look things up.

do kde-svnbuild and build-tool satisfy this well enough?
or do we want a computer-readable file listing all the repos too?

btw, scripty has its own list of repos already. it's just in a rather weird bash file.

'''Links'''
[http://kdesvn-build.kde.org/]
[[Projects/MovetoGit/MassCloneScript]]
[http://rubyforge.org/projects/build-tool/]

==pre-receive hooks==
{{Progress bar|0}}
'''Owner:''' ''volunteers needed!!''

* Line endings and encodings

'''Discussion:'''
this got accidentally marked as done or something, but it's not.

'''Notes:'''
> > As for line-endings, be careful because Git is different from Subversion.
>
> different how?

Just ensure that all files are stored as LF only, except if there's a
.gitattributes file saying "-crlf" (i.e., allow it to have CRLF).

==Snapshot to read-only svn==
{{Progress bar|0}}
'''Owner:'''

:It's work, but maybe some people would like it. NEEDED for documentation, in order to get it back into SVN for the translators/scripty/?

'''Discussion'''

:Could be done with a git-svn gateway presumably? -Mike Arthur 19/10/2009 16:04

:if we leave the docbook stuff in svn, we can avoid this a bit longer. --[[User:Chani|Chani]] 23:21, 12 November 2009 (UTC)

==[[Development/Tutorials/Git|Techbase Documentation]]==
'''Owner:''' Chani, greeneg, - ''please help out!''
{{Progress bar|10}}

:At least minimal documentation about how to checkout, how to get a Gitorious account, how to request a merge needed, other git documentation and links to other git information would be very useful also.

:see the [[Development/Tutorials/Git|Git Tutorial Page]]. help wanted!!

'''Discussion'''

==Setup git mirrors for cloning==
{{Progress bar|0}}
'''Owner:''' No one (help!)
:Re-purpose the anonsvn servers. This item might be a blocker.
'''Discussion'''

==Local pre-commit hooks==
{{Progress bar|0}}
'''Owner:''' argonel

:A set of recommended local hooks that give useful warnings could be nice to have.

'''Discussion'''
...on the other hand, if we get a lot of bikeshedding about what hooks, then it won't be so nice. so I'd put this in the "very optional" pile. --[[User:Chani|Chani]] 19:10, 16 December 2009 (UTC)

=Post-migration Issues=

==Website Branding==
{{Progress bar|2|text=(initial ideas on the table)}}
'''Owner:''' ruphy

:KDE Gitorious should be branded accordingly, and should be reachable from git.kde.org as well as kde.gitorious.org

'''Discussion'''

=Unscheduled & Open=

==Allow tagging without involving sysadmins==
{{Progress bar|0}}

'''Owner:''' johan

:Pushing a tag currently requires permissions to do a force push, which is a repository-wide checkbox that can only be toggled by a kde-developers admin. Thus the workflow for a dev wanting to do a release tag for his app is to ask an admin to enable force pushing, then to push his tag, and then to tell the admin he can disable force pushing again. This doesn't scale, is insecure, and at odds with KDE's open access policy when it comes to managing the repos (right now in SVN, you need sysadmin to create an app dir in /tags for you, but don't have to ask permission for every individual tag). Johan has promised a solution for this.

:Notable discussion points on kde-scm-interest:
:http://mail.kde.org/pipermail/kde-scm-interest/2009-November/000782.html
:http://mail.kde.org/pipermail/kde-scm-interest/2009-November/000784.html

'''Discussion'''

==Account setup on Gitorious==
{{Progress bar|0}}

'''Owner:''' ''eean, johan, boud, dario''

:Creating an account on Gitorious isn't hard, but asking to be added to the KDE group is inconvenient. For the migration we should set up a system (via email or wiki?) where developers can ask to have an account autocreated for them, or add their existing Gitorious account to a list to be added to the group. Once this is in place an announcement should be sent to all svn accounts explaining the process, and privacy information.

:Basically the currently method of using Bugzilla works fine now and works fine in the longterm. But in the transition month when hundreds of accounts must be created or added, we need a better system. Its important to make it as easy as possible so that we don't lose anyone in the shuffle.

'''Discussion'''

: I think most people have made their own accounts by now. this isn't really needed.

==post-update hooks==
{{Progress bar|90}}
'''Owner:''' ''morice'' ''Ian Monroe''

:* License checker

'''Discussion:'''
We have a fairly complete set of post-update hooks now. See [http://gitorious.org/remotehook remotehook]. However, it would be nice to have a system that lives on the Gitorious server and/or requires less manual maintenance. But its certainly workable and no longer a blocker.

=Completed Tasks=

==Get rid of svn:externals==
{{Progress bar|100}}
'''Owner:''' David Faure

'''Status:''' ''???''

:not possible with git, broken by design.

::

'''Discussion'''

Exists, but ignorable:
* kdesupport shared-desktop-ontologies (temporary)
* playground/utils strigi-chemical/test/ctfr
* playground/devtools kdevelop4-extra-plugins/php/parser/generated/kdevelop-pg-qt
* playground/devtools kdevelop4-extra-plugins/python/parser/generated/kdevelop-pg-qt
* playground/devtools kdevelop4-extra-plugins/qmake/parser/generated/kdevelop-pg-qt
* playground/devtools kommander-plugins/database3/admin
* playground/devtools kommander-plugins/database/admin
* playground/devtools kommander-plugins/datetimefuncs/admin
* playground/devtools kommander-plugins/htmlpart/admin
* playground/devtools kommander-plugins/httpform/admin
* playground/devtools kommander-plugins/kparts/admin
* playground/devtools kommander-plugins/qtactionproxy/admin
* playground/devtools kommander-plugins/timewidget/admin
* playground/devtools kommander-plugins/webkit3/admin
* playground/devtools kpackagemaker/admin

==EBN==
{{Progress bar|95}}
'''Owner:''' ''drf''

'''Status:''' ''Amarok has EBN checks''

:EBN's krazy checks currently run on kde's svn repo; it needs upgrading to download and check our git repos too.

:This would be easier if there was a repo-list that EBN could parse, as it can no longer just svn up to get everything.

==Talk to people using other distros about git==
{{Progress bar|100}}
'''Owner:''' Sebas, Eike

'''Discussion'''
* Gentoo: They seem to be prepared for moving their live SVN packages to git; their package manager has easily-reusable classes to fetch from an SCM and moving the ebuilds to using the git class rather than the SVN class should be easy. Positive comments to that end from people in #gentoo-kde.
* Fedora: Some unhappyness about git because SVN allows them to remotely produce a diff between two SVN URLs (or two revisions of one and the same URL) without making a checkout first, while git requires making a clone. Kevin Kofler (IRC nick Kevin_Kofler, #fedora-kde) says this will make their packager work harder.
* Debian: Is indifferent about the SCM switch.

==Post Update hooks==
{{Progress bar|100}}
'''Owner:''' ''morice, johan, mattr

:List of scripts needed:
:* BUG/CCMAIL
:* email/CIA

:Gitorious needs to provide a way for hooks to be called; KDE needs to write said hooks.

'''Discussion'''

:There is a branch of gitorious called web-hooks http://gitorious.org/gitorious/mainline/commits/web-hooks --Panagiotis Papadopoulos 1 November 2009
:Same situation as commit emails. I can do it but it doesn't scale well and a Gitorious-supported solution would be nicer. --[[User:Eean|eean]] 16:07, 12 November 2009 (UTC)

==Opt-in privacy exception required for kde-developers==
<strike>
{{Progress bar|0}}
'''Owner:''' ''Gitorious'', ''KDE e.V. Board'', ''eean''

:KDE sysadmins need access to some information that Shortcut could not give them due to their privacy policy. Examples include an email list of all the developers and SQL-level access to information about all the repos in KDE (since it stores who pushes what, information not stored in the git repo itself).

:Such requirements will likely be put into the contract with Shortcut.

'''Discussion'''
:So the e.V. Board is an owner since this is a legal/contract/money issue. Added myself only because I'm shepherding the issue. --[[User:Eean|eean]] 16:16, 12 November 2009 (UTC)

</strike>

:'''We will not get sql access to the information. For the alternative solution see the Push Log issue'''

==Reviewboard==
{{Progress bar|100}}
'''Owner:''' darktears

This should be easily done with Gitorious web interface and merge requests actually.

'''Discussion'''

:but reviewboard has features gitorious (right now) doesn't, like commenting on specific lines and not having to set up a merge request. --chani
::Also email notifications when someone reviews are needed --thomasz
:We're working on this for someone else right now, so pretty soon --johan-s
:I consider the latest changes to gitorious to finish this. If more reviewboard features are still needed, and git supports reviewboard, I think this is something we can look at doing post-conversion. --Ian Monroe

==Gitorious Needs a feature to disable merge request emails for certain repos==
{{Progress bar|100}}
'''Owner:''' [http://gitorious.org/gitorious Gitorious]

Have a sensible system for merge request emails. This is now in place - you can join groups, chose whether to have emails on a per repo basis, etc.

==SSH blocked in corporations and universities.==
{{Progress bar|100}}
'''Owner:''' ''Unknown''

:Some universities tend to block the SSH port. There should be a workaround to use SSH on some different port. github.com already runs a SSH server on port 443. But that assumes you are using a proxy. It has been found that this hasn't worked with a lot of people, especially those who have a direct connection to the internet ( so some transparent blocking by the ISP ). It would be great if (almost) every KDE developer were to be asked to check if other ports work before KDE made the switch. Otherwise there could be an automated email where the git patches could be sent, and appropriately patched to the right location too.

'''Discussion'''

:http://blog.gitorious.org/2009/10/20/stuck-behind-a-firewall/, and there's always been HTTP cloning (although the current impl. in Git is a bit on the slow side) --johan-s

==Talk to windows guys about git.==
{{Progress bar|100}}
'''Owner:''' aseigo

'''Discussion'''

They aren't huge fans of git, but are using it. They require a single mainline and can't cope with multiple branches. Otherwise, it's workable, even if it will take an adjustment period.

==pre-commit hooks==
{{Progress bar|100}}
'''Owner:''' ''(unknown)''

:acltest, docbook, EOL/UTF-8

:A web hook isn't good enough for these because they have to run and return whether to allow the push, for every single push to every KDE repo.

'''Discussion'''

:gitorious guys said they *might* be willing to allow a few scripts on their server for KDE as a special exception, iirc. --chani

:: Yes, at least for basic things, heavier things like doc building would probably have to be mirrored (goes for pre/post) --johan-s

:It turns out that acl and docbook might not be needed so long as web and docs/ stuff stays in svn.

:: Here's where to find the current scripts - http://websvn.kde.org/trunk/kde-common/svn/hooks/ --[[User:Argonel|Argonel]] 23:06, 11 November 2009 (UTC)

::So: this is actually done because it needs no longer to be done? (boud)

::Apparently, so; moving to complete. (aseigo)

= other notes =

==kde-common/accounts==

Someone said: KDE accounts file is no longer necessary---used for mapping svn ID -> email, but we have that now from Gitorious.
Answer from David Faure: I strongly disagree. We still need a KDE accounts file. This is very useful for finding people's email addresses, and having an overview on the number of active kde contributors; and if we keep it we can even have a kdepim resource again for filling an addressbook from it, for completion in kmail's composer (so you can write to any other kde contributor by just typing his/her name). It's also used for populating automatically the kde-cvs-announce mailing-list, for announcements. kde-common/accounts is our family tree (well, list), let's not get rid of it.

Here's my proposal for a kde-common/accounts replacement for the git era: We write a post-receive hook that looks at every commit and records all known email addresses for a given real name as well as the commit hash and date of when an address was last encountered. We can then present that data in the form of a file like kde-common/accounts, or write a web interface to query it (with nice links to the commits on Gitorious, etc.) --Eike (Sho_ on IRC)

To clear up possible confusion: The author information for a given commit is baked into the commit object itself, and comes from the configuration of the git repository it was created in. It is unrelated to any Gitorious account. Due to the distributed nature of Git, the one who uses his Gitorious account to push a commit need not be the same who created it. If Developer A creates a commit in his local clone and Developer B fetches it into his local clone directly from Developer A's machine and then pushes it into the public repo, the repo will only show a commit from Developer A. The Gitorious website will show that Developer B has pushed up a commit from Developer A, but that data is not contained in the repository. Thus collecting only Gitorious accounts and their mail addresses is insufficient. --Eike

==Random==
http://mail.kde.org/pipermail/dot-stories/2005-May/000509.html might be a good guide on what docs we need.

some of this stuff was from the list from GCDS that was in this email [http://markmail.org/message/u6eqfjece7fibfyo http://markmail.org/message/u6eqfjece7fibfyo]

==IRC Meetings==
* [[Projects/MovetoGit/Meeting1111|Minutes]] of meeting 11 November 2009
* [[Projects/MovetoGit/Meeting1118|Next meeting]] 18:00, 25 November 2009 (UTC)

= jobs =
''TODO merge this with the todolists above''

michael jansen: talking to kdesvn-build/mpyne
:--Done? -> http://kdesvn-build.kde.org/releases/kdesvn-build-1.10.php -- Panagiotis Papadopoulos 1 November 2009
::Yes, but the __kdesvn-build-remote used in the impl isn't pleasant for users already on git so it still needs more work for them. [[User:Mpyne|Mpyne]] 20:32, 11 November 2009 (UTC)

jonas: domain name

ML: convert to SSH

chani: techbase docs for scripty

sebas/lydia/leo: communication with teams! tell people! keeping track that
everything is being done.

Archive:Development/Tutorials/Git/KdeOnGit

2010-04-16T17:27:49Z

Santa: Fix typo s/Albert Astaid/Albert Astals/

Currently, Amarok and Konversation are testing out git to help with KDE's migration. There are also one or two kde-related projects that have started on [http://gitorious.org/about gitorious] (although this is *not* recommended yet!)

TODO:
* Explain where to find various kde projects and modules.
* Explain how to clone them.
* readonly-use guide
* contributing:
** quick guide to gitorious website (copy content from amarok) (this should probably be spread between this page and the [[Development/Tutorials/Git/Pushing|Pushing]] one.)

==How KDE projects on Gitorious.org are set up==

First up, a brief description of the Gitorious.org user and permission model:

* Individual user accounts can be organized into teams. Teams have members and administrators. Administrators can add new members and administrators, as well as edit a team's description.

* A project can be owned by either a team or an individual user account. A project can have one or more repositories.

* Any individual repository has a list of collaborators. A collaborator can be either a team or an individual user account and can have any combination of these three flags: commit (allows pushing commits), admin (allows editing the repository's description and settings, including the collaborator list) and review (allows processing merge requests).

KDE currently operates the [http://gitorious.org/+kde-developers kde-developers] and [http://gitorious.org/+kde-sysadmin kde-sysadmin] teams on Gitorious.org, as well as several <appname>-reviewers teams (e.g. [http://gitorious.org/+konversation-reviewers konversation-reviewers]). The purpose of each of these can best be illustrated by examining how a KDE project on Gitorious.org has to be set up:

* The project is owned by kde-developers.
* The repositories belonging to the project have the 'kde-developers' team as a collaborator with the and only the 'commit' flag.
* The repositories also have 'kde-sysadmin' as a collaborator, with the and only the 'admin' flag.
* And they have an '<appname>-reviewers' team as a collaborator with the and only the 'review' flag.
* They also optionally have one or more key developers of the project as collaborators with the and only the 'admin' flag.

Commit access is thus handled exclusively via kde-developers, and any member of kde-developers can commit to any KDE repository. Getting into kde-developers is done by [https://bugs.kde.org/enter_sysadmin_request.cgi?component=gitorious filing a KDE sysadmin request against the gitorious component], which is then implemented by one of the administrators of the kde-developers team.

The kde-sysadmin team exists for the purpose of making sure KDE's sysadmin squad can edit all KDE repositories on Gitorious.org, to fix issues or help people in a bind.

The '<appname>-reviewers' teams were originally created to be able to remove the 'review' flag from kde-developers for all the repositories, because otherwise every kde-developers member got email notifications about every merge request for every project. So someone with no interest in Amarok or Konversation would still get MR mail about them. Project-specific reviewers teams solve that routing problem. The reviewers teams usually have all the core developers from a project as members, and are administrated by one or more key developers.

Now, about those optionally-added key developers with the 'admin' flag: Pushing a tag into a repository requires being allowed to do a "force push". Force pushing can be enabled/disabled on a per-repository basis on Gitorious.org by anyone who has the 'admin' flag for a repository. As outlined above, this currently means every member of the kde-sysadmin team - as well as one or more key developers from a given project that have been added individually with the 'admin' flag. Thus the the main motivation for this is to allow projects to push tags without having to involve KDE's sysadmin team.

=== Enable post-update hooks ===

The post-update hooks enable features like the CCMAIL:, BUG: filters and emails the kde-commits mailing list.

The [http://gitorious.org/remotehook remote hooks] repo has the scripts that set all this up. However just send the old SVN url and the new git:// url to Ian Monroe (eean in #kde-git) and he will set it up on the Amarok server.

==Projects already on Gitorious==

* [http://gitorious.org/amarok Amarok] - KDE's favorite music player.
* [http://gitorious.org/konversation Konversation] - an IRC client for KDE.
* [http://gitorious.org/+kde-developers/qt/kde-qt kde-qt] - KDE’s copy of Qt, containing the latest release, plus patches for Qt that haven’t been accepted (yet) by Qt Software.
FIXME: Is this a KDE project? Why are permissions not set for kde-developers?
* [http://www.gitorious.org/project-silk Project Silk] - We've been working with gitorious as an experiment.

http://gitorious.org/+kde-developers has a more up-to-date list of kde-run projects. However, that list includes projects that don't use kde frameworks (like KDE developers' personal projects), and experiments, and isn't sorted in any way. We plan to have a better directory of kde-related projects once git.kde.org is up.

== Setting up your KDE project to start developing in Gitorious ==

Ok, consider that things are ready to move your own project to Gitorious and you wanna know what you have to do. Let's start doing it together.

First of all, you should subscribe to Gitorious and move there your project. This will not be explained here... :)

Now you need to ask KDE sysadmins from [https://bugs.kde.org/enter_sysadmin_request.cgi here] to include your account in the +kde-developers group.
Give a couple of days to sysadmins to value your request and (hopefully) accept it.
Now you have one project in Gitorious (and you own it) created with an account included in kde-developers group.

Next step is moving ownership of your project to the group. In this way, every kde developer will be enabled to collaborate to your project. :)
To do this, mail Gitorious support [mailto:support@gitorious.org team] asking to move yourproject ownership to the kde-developers group.
Given that, you have to ask again KDE sysadmin to properly set up your project. Just read about that, didn't you?

Now your repository is quite ready. You need still to do just something:

* ask Albert Astals Cid to point the scripty bot to your git repo (He'll ask you your main branch name and your repo push url)
* ask Ian Monroe to add the post commit hooks to your repo, to let things as the keyword BUG: and CCBUG: work
* ask (again) the KDE sysadmins to get integration into lxr.kde.org working
* ask Allen Winter to get integration into EBN working
(note: can I include their kde mail here?)

That's all! In a couple of days your git repo will be ready.

Happy hacking with KDE!

Development/Architecture/KDE3/i18n and l10n

2009-11-02T13:55:13Z

Santa: Fixed programming lang. s/cppqt3/cppqt/

{{Template:I18n/Language Navigation Bar|Development/Architecture/KDE3/i18n and l10n}}

Reaching a broad audience of users and developers requires that your software can be translated and otherwise shaped at runtime to be linguistically and culturally relevant to whomever is sitting in front of the computer. This is the realm of localization and this tutorial steps you through what is needed to make your application localizable.

== What is Internationalization and Localization? ==

Internationalization, or i18n ('i', followed by 18 letters, then an 'n'), is the process of writing your application so that it can be run in any locale. This means taking into account such things as:
* textual messages that are displayed to the user
* data input from the user, files and other sources
* format of dates, numbers, currency, dates, etc.

Localization, or l10n ('l', followed by 10 characters, then an 'n'), is the process of taking an internationalized application and adapting it for a specific locale.

Generaly speaking, programmers internationalize their applications and translation teams localize them.

== Why is This Important? ==

KDE development happens primarily in English as this allows the broadest reach into the development and translation communities. However, English is not the primary language of most people on the planet. In fact, fewer than 8% of humanity speaks English and less than 5% speak it as their mother tongue. Even on the Internet, only 35% people who are online use English as their primary language and as more and more of the world gets wired this number is only decreasing. Additionally most languages, including 9 out of the 10 most common languages, use non-ASCII characters in their written form. It is easy to see, then, why it has become a necessity to provide localized software.

As an international project that spans the globe such localization is a core value within the KDE culture. In fact, while many KDE developers write their software in English they use the desktop in their native locale.

== Translatable Code Using i18n() ==

To ensure applications are ready to be localized they have to follow a few simple rules. All user-visible strings in the application should be translated before they are displayed on the user's screen, exceptions to this being debugging messages, configuration keys and similar types of text data.

KDE provides the <tt>KLocale</tt> class as part of <tt>libkdecore</tt> to facilitate the technical details of localization. KLocale makes it as easy as possible for developers to make their code i18n aware, but there are some things they need to be aware of so that applications are usable in other languages and countries.

Access to a global <tt>KLocale</tt> object is provided via <tt>KGlobal::locale()</tt>. This <tt>KLocale</tt> object is created automatically by <tt>KInstance</tt> and takes care of all user i18n related settings. It is deleted automatically on application exit.

Translations are made possible by the <tt>QString i18n(const char*)</tt> method which must wrap all strings that should be displayed. The QString returned by <tt>i18n()</tt> is the translated (if necessary) string. This makes creating translatable widgets as simple as in this example:

<code cppqt>
QPushButton* myButton = new QPushButton(i18n("Translate this!"), 0);</code>

QString's native Unicode support ensures that all translations are represented correctly. All string handling done by your application should therefore use QString.

{{tip|If the string to be translated contains any non-UTF8 characters, use the utf8() method to get a char*.}}

=== I18N_NOOP ===

The <tt>i18n()</tt> method requires that a <tt>KInstance</tt> (e.g. <tt>KApplication</tt>) has been created. For any strings that are created prior to this there is a macro provided: I18N_NOOP(). This allows one to mark strings that should be translated later as such.

When you want to actually translate the string at runtime, you still have to use i18n() with exactly the same string. I18N_NOOP() is typically used for strings given to KAboutData, because it is constructed before the KApplication and you can use i18n() only after the construction of the KApplication. Other than these special cases, it is always safe to use i18n() if you are sure that the code will be executed after construction of KApplication or some other KInstance.

=== Adding Context ===

There is an extended version of <tt>i18n()</tt> which takes two <tt>const char*</tt> arguments. The first argument is an additional contextual description of the second, translated string. The first string is used to find the proper corresponding translation at run-time and is shown to translators to help them understand the meaning of the string.

Use this variety of <tt>i18n()</tt> when the purpose of the text might be ambiguous without further context. For example, consider a context menu in a file manager with an entry called "View" which opens a viewer for the currently selected file. In this context "View" is a verb. However, the same application also may have a menu called "View" in the menubar. In that context "View" is a noun. In the English version of the application everything looks fine, but in most other languages one of the two "View" strings will be incorrect.

Additionally, translators sometimes need extra help in understanding what the text is actually referring to during the translation purpose. Use this form of i18n whenever the string to translate is short or the meaning is hard to discern when the context is not exactly known. For example:

<code cppqt>QString up = i18n("Go one directory up in the hierarchy", "Up");
QString relation = i18n("A person's name and their familial relationship to you.", "%1 is your %2").arg(name, relationship);</code>

{{note|There is also a I18N_NOOP2("context","text") macro for providing untranslated strings with a context.}}

=== Plurals ===

Plurals are handled differently from language to language. Many languages have different plurals for 2, 10, 20, 100, etc. When the string you want translated refers to more than one item, you must use the third form of <tt>i18n</tt>: <tt>QString i18n(const char* singular, const char* plural, int number)</tt>. For example:

<code cppqt>msgStr = i18n("Creating index file: 1 message done",
"Creating index file: %n messages done", num);</code>

This form of <tt>i18n()</tt> gets expanded to as many cases as required by the user's language. In English, this is just two forms while in other languages it may be more depending on the value of the <tt>number</tt> parameter.

Note that this form should be used even if the string always refers to more than one item as languages use a singular form even when referring to a multiple (typically for 21, 31, etc.). This code:

<code cppqt>i18n("%1 files were deleted").arg(numFilesDeleted);</code>

is therefore incorrect and should instead be:

<code cppqt>i18n("%1 files were deleted",
"%1 files were deleted",
numFilesDeleted).arg(numFilesDeleted);</code>

== Formatting Dates and Numbers ==

When displaying a number to the user, your program must take care of the decimal separator, thousand separator and currency symbol (if any) being used. These symbols differ from region to region. In English speaking countries a dot (.) is used to separate the fractional part of a number, while in some European countries a comma (,) is used instead. Below is a short summary of functions that will help you format the numbers correctly, taking the local conventions into account for you.

{|
|+ Functions to Format Numbers
|-
! Formats a.. !! From a.. !! Function Prototype
|-
| Number || String || <pre>QString formatNumber( const QString & numStr )</pre>
|-
| Number || Integer, double || <pre>formatNumber( double num,
int precision = -1 )</pre>
|-
| Money || String || <pre>formatMoney( const QString & numStr )</pre>
|-
| Money || Number || <pre>formatMoney( double num,
const QString & currency,
int digits = -1 )</pre>
|-
| Date || String || <pre>formatDate( const QDate & pDate,
bool shortFormat=false )</pre>
|-
| Time || {{qt3|QTime}} || <pre>formatTime( const QTime & pTime,
bool includeSecs=false)</pre>
|-
| Date and time || {{qt3|QDateTime}} || <pre>formatDateTime( const QDateTime &pDateTime,
bool shortFormat = true,
bool includeSecs = false )</pre>
|}

Similar functions exist to read information provided by the user at runtime in their localized format, e.g. readNumber() or readMoney().

== Calendaring ==

Developing applications dealing with dates and time, such as calendars, is a very complex area. Not only may the displayed string containing a date or time may look different based on locale, but one also has to take care of other aspects such as:
* which day in the week is the first one (cf int weekStartDay())
* how many months in a year there are
* "era"-based calendars
* whether to use 24-hour time format (cf bool use12Clock())

KLocale provides, among others, these methods:

{|
|+ Calendar Data Functions
|-
! Formats a.. !! From a.. !! Function Prototype
|-
| Date || /klocal/QDate || <pre>formatDate( const QDate & pDate,
bool shortFormat=false )</pre>
|-
| Time || {{qt3|QTime}} || <pre>formatTime( const QTime & pTime,
bool includeSecs=false )</pre>
|-
| Date and time || {{qt3|QDateTime}} || <pre>formatDateTime( const QDateTime &pDateTime,
bool shortFormat=true,
bool includeSecs=false )</pre>
|}

== Further Information ==
For additional information have a look at the [http://i18n.kde.org i18n pages].

[[Category:KDE3]]
[[Category:Architecture]]

Development/Tools

2009-10-12T01:09:24Z

Santa: /* Quality Assurance */ Fix typo

{{Template:I18n/Language Navigation Bar|Development/Tools}}
This section contains information about tools for KDE development.

== Debugging and Analysis ==
A list of tools which are used to analyze a program. This includes debuggers and profilers, for instance.

; Valgrind
: [[Development/Tools/Valgrind|Valgrind]] helps to find memory leaks and uninitialized memory blocks. Additional features are a profiler and more. Valgrind is one of the most important development tools!

; The GNU Project Debugger (GDB)
: [http://sources.redhat.com/gdb/ GDB] helps in debugging source code. As GDB evolved over time it is recommended to use version 6.x. Graphical frontends are available (see below). See also the debugging tutorial [[../Tutorials/Debugging/Debugging with GDB|Debugging with GDB]].

; KDbg and DDD
: [http://www.kdbg.org/ KDbg] and [http://www.gnu.org/software/ddd/ DDD] are graphical user interfaces to GDB, which are able to set breakpoints, step through the code etc.

; MS Windows tools (Process Explorer, Console, WinDbg, DebugView...)
: More info on the [[Projects/KDE_on_Windows/Tools|KDE on Windows page]].

== Development Tools ==
; KDevelop
: [http://www.kdevelop.org KDevelop] is an excellent IDE for developing KDE and Qt C++ applications. It includes a an integrated debugger, a powerful editor with syntax highlighting, a ''Project wizard'' to create applications from templates, the automake/autoconf gunk, and even the class documentation. Further details can also be found in the [http://kdevelop.org/mediawiki/index.php/Main_Page KDevelop wiki].

:Instructions on how to use KDevelop with KDE 4 applications is available at [[Getting_Started/Set_up_KDE_4_for_development#KDevelop|this page]]

; Qt Designer
: With Trolltechs [http://www.trolltech.com/products/qt/features/designer Qt Designer] it is easy to layout user interfaces like buttons and checkboxes. Additional features are undo/redo, checking accelerator conflicts etc. Qt Designer allows even non-programmers to help design KDE dialogs. Further details can be found in the tutorial [[Development/Tutorials/Using_Qt_Designer|Using Qt Designer]] and in the [http://doc.trolltech.com/4.2/designer-manual.html Qt documentation].

; MS Visual Studio® Express 2005 IDE (Windows only)
: Visual C++® 2005 Express Edition [http://www.microsoft.com/germany/msdn/vstudio/products/express/visualc/default.mspx] is the free version of the Microsoft Visual Studio 2005 compiler from Microsoft, which is officially supported by Trolltech since Qt 4.3.2. It is a choice for compiling Qt and KDE applications on Windows. [[Projects/KDE_on_Windows/Issues/MSVC|more info...]]

== Internationalization (i18n) Tools ==

; KBabel
: [http://kbabel.kde.org/ KBabel] is a set of tools for editing and managing gettext PO files. Its main part is a powerful and comfortable PO file editor which features full navigation capabilities, full editing functionality, possibility to search for translations in different dictionaries, spell and syntax checking, showing diffs and many more.

: Also included is a "Catalog Manager", a file manager view which helps in keeping an overview of PO files. Last but not least it includes a standalone dictionary application as an additional possibility to access KBabel's powerful dictionaries. KBabel will help you to translate fast and also keep consistent translations.

; Dr. Klash
: This little utility, once activated, can present a report about conflicting shortcuts in menus. Not only is this helpful for translators but also for developers. A little hand editing of {{path|`kde-config --localprefix`/share/config/kdeglobals}} activates this feature:

<code ini>
[Development]
CheckAccelerators=F12
AutoCheckAccelerators=false
AlwaysShowCheckAccelerators=false
</code>

: Pressing F12 will show a dialog containing which accelerators in the currently focussed interface conflict and provide suggestions for new accelerators. If no accelerators conflict or Dr. Klash has nothing to suggest, no popup dialog will be displayed.

: With <tt>AutoCheckAccelerators</tt> enabled the dialog will popup automatically if a conflict exists and <tt>AlwaysShowCheckAccelerators</tt> can force the dialog to always popup even if there are no conflicts to report.

; The x-test language
: This helper language serves as a debugging aid for people finding untranslated strings in applications. If you start your application with the "x-test" locale, all translated strings will appear with trailing and leading xx's. First you have to check out these "translations" from l10n-kde4/x-test and install them.

: After you've built l10n-kde4/x-test and installed it, run your application using the "x-test" locale. This can be done by launching it from the command line like this:

> KDE_LANG=x-test kspread

: This will start KSpread using the "x-test" locale no matter what your current language setting is. Look for strings that do not have the xx's. If xx's are missing from a string, it could be due to missing i18n calls or even missing or incorrectly generated .pot files. Consult the i18n tutorials for further information.

: When checking for untranslated strings, be sure to check all the WhatsThis help and tooltips.

=== Examining .po files ===

You can look at the translated .po files to see if a string is present and has been translated. For example, here's a portion of {{path|l10n/de/messages/kdebase/konqueror.po}}:

#: konq_mainwindow.cc:3707 konq_tabs.cc:84
msgid "&New Tab"
msgstr "Neues &Unterfenster"

The string to be translated is given on the msgid line. The translated string is on the msgstr line. Notice that the exact same string to translate came from {{path|konq_mainwindow.cc}} and also from {{path|konq_tabs.cc}}. This saves the translators from having to translate the same identical string twice.

You can also use KBabel to examine {{path|.po}} files. KBabel is part of the kdesdk module.

{{note|More information on writing and translating documentation can be found on [http://l10n.kde.org/ the l10n project site].}}

== Helper Tools ==

; [[Development/Tools/Using kde-config|Get information about KDE's installation - kde-config]]
: The tool kde-config helps to find out more about a KDE installation.

; [[Development/Tools/Using kfmclient|Driving Konqueror From Scripts - kfmclient]]
: kfmclient is a small tool to communicate with Konqueror.

;[[Development/Tools/Using kconf_update|Updating User Configuration Files - kconf_update]]
: kconf_update is a tool designed to update config files.

;[[Development/Tools/apidox|Generating apidox]]
: tools that help develop and generate API documentation for your code.

;[[Development/Tools/Automoc4|Automoc4]]
: This is a helper tool needed to build KDE4. It automatically generates moc-files.

;[[Development/Tools/svnmerge.py|svnmerge.py]]
: This tool helps keeping track of merges between different SVN branches

== Quality Assurance ==

; Continuous Building - Dashboard
: [http://developer.kde.org/~dirk/dashboard/ all kde modules on Dirk's dashboard]
: [http://winkde.org/pub/kde/ports/win32/dashboard/ some kde software on win32 dashboard]
: [http://public.kitware.com/dashboard.php?name=kde kdelibs on kitware]

; [http://englishbreakfastnetwork.org/ English Breakfast Network] - Static Analysis
: [http://www.englishbreakfastnetwork.org/krazy/ Krazy ] - Code Analysis, [[Development/Tutorials/Code_Checking|Usage Tutorial]]
: [http://www.englishbreakfastnetwork.org/apidocs/ APIDOX] - API Documentation Statistics
: [http://www.englishbreakfastnetwork.org/sanitizer/ Sanitizer] - DocBook Checker
: [http://www.englishbreakfastnetwork.org/usability/ Usability Checks]

Development/Tools

2009-10-12T01:08:50Z

Santa: /* Quality Assurance */ Add win32 dashboard.

{{Template:I18n/Language Navigation Bar|Development/Tools}}
This section contains information about tools for KDE development.

== Debugging and Analysis ==
A list of tools which are used to analyze a program. This includes debuggers and profilers, for instance.

; Valgrind
: [[Development/Tools/Valgrind|Valgrind]] helps to find memory leaks and uninitialized memory blocks. Additional features are a profiler and more. Valgrind is one of the most important development tools!

; The GNU Project Debugger (GDB)
: [http://sources.redhat.com/gdb/ GDB] helps in debugging source code. As GDB evolved over time it is recommended to use version 6.x. Graphical frontends are available (see below). See also the debugging tutorial [[../Tutorials/Debugging/Debugging with GDB|Debugging with GDB]].

; KDbg and DDD
: [http://www.kdbg.org/ KDbg] and [http://www.gnu.org/software/ddd/ DDD] are graphical user interfaces to GDB, which are able to set breakpoints, step through the code etc.

; MS Windows tools (Process Explorer, Console, WinDbg, DebugView...)
: More info on the [[Projects/KDE_on_Windows/Tools|KDE on Windows page]].

== Development Tools ==
; KDevelop
: [http://www.kdevelop.org KDevelop] is an excellent IDE for developing KDE and Qt C++ applications. It includes a an integrated debugger, a powerful editor with syntax highlighting, a ''Project wizard'' to create applications from templates, the automake/autoconf gunk, and even the class documentation. Further details can also be found in the [http://kdevelop.org/mediawiki/index.php/Main_Page KDevelop wiki].

:Instructions on how to use KDevelop with KDE 4 applications is available at [[Getting_Started/Set_up_KDE_4_for_development#KDevelop|this page]]

; Qt Designer
: With Trolltechs [http://www.trolltech.com/products/qt/features/designer Qt Designer] it is easy to layout user interfaces like buttons and checkboxes. Additional features are undo/redo, checking accelerator conflicts etc. Qt Designer allows even non-programmers to help design KDE dialogs. Further details can be found in the tutorial [[Development/Tutorials/Using_Qt_Designer|Using Qt Designer]] and in the [http://doc.trolltech.com/4.2/designer-manual.html Qt documentation].

; MS Visual Studio® Express 2005 IDE (Windows only)
: Visual C++® 2005 Express Edition [http://www.microsoft.com/germany/msdn/vstudio/products/express/visualc/default.mspx] is the free version of the Microsoft Visual Studio 2005 compiler from Microsoft, which is officially supported by Trolltech since Qt 4.3.2. It is a choice for compiling Qt and KDE applications on Windows. [[Projects/KDE_on_Windows/Issues/MSVC|more info...]]

== Internationalization (i18n) Tools ==

; KBabel
: [http://kbabel.kde.org/ KBabel] is a set of tools for editing and managing gettext PO files. Its main part is a powerful and comfortable PO file editor which features full navigation capabilities, full editing functionality, possibility to search for translations in different dictionaries, spell and syntax checking, showing diffs and many more.

: Also included is a "Catalog Manager", a file manager view which helps in keeping an overview of PO files. Last but not least it includes a standalone dictionary application as an additional possibility to access KBabel's powerful dictionaries. KBabel will help you to translate fast and also keep consistent translations.

; Dr. Klash
: This little utility, once activated, can present a report about conflicting shortcuts in menus. Not only is this helpful for translators but also for developers. A little hand editing of {{path|`kde-config --localprefix`/share/config/kdeglobals}} activates this feature:

<code ini>
[Development]
CheckAccelerators=F12
AutoCheckAccelerators=false
AlwaysShowCheckAccelerators=false
</code>

: Pressing F12 will show a dialog containing which accelerators in the currently focussed interface conflict and provide suggestions for new accelerators. If no accelerators conflict or Dr. Klash has nothing to suggest, no popup dialog will be displayed.

: With <tt>AutoCheckAccelerators</tt> enabled the dialog will popup automatically if a conflict exists and <tt>AlwaysShowCheckAccelerators</tt> can force the dialog to always popup even if there are no conflicts to report.

; The x-test language
: This helper language serves as a debugging aid for people finding untranslated strings in applications. If you start your application with the "x-test" locale, all translated strings will appear with trailing and leading xx's. First you have to check out these "translations" from l10n-kde4/x-test and install them.

: After you've built l10n-kde4/x-test and installed it, run your application using the "x-test" locale. This can be done by launching it from the command line like this:

> KDE_LANG=x-test kspread

: This will start KSpread using the "x-test" locale no matter what your current language setting is. Look for strings that do not have the xx's. If xx's are missing from a string, it could be due to missing i18n calls or even missing or incorrectly generated .pot files. Consult the i18n tutorials for further information.

: When checking for untranslated strings, be sure to check all the WhatsThis help and tooltips.

=== Examining .po files ===

You can look at the translated .po files to see if a string is present and has been translated. For example, here's a portion of {{path|l10n/de/messages/kdebase/konqueror.po}}:

#: konq_mainwindow.cc:3707 konq_tabs.cc:84
msgid "&New Tab"
msgstr "Neues &Unterfenster"

The string to be translated is given on the msgid line. The translated string is on the msgstr line. Notice that the exact same string to translate came from {{path|konq_mainwindow.cc}} and also from {{path|konq_tabs.cc}}. This saves the translators from having to translate the same identical string twice.

You can also use KBabel to examine {{path|.po}} files. KBabel is part of the kdesdk module.

{{note|More information on writing and translating documentation can be found on [http://l10n.kde.org/ the l10n project site].}}

== Helper Tools ==

; [[Development/Tools/Using kde-config|Get information about KDE's installation - kde-config]]
: The tool kde-config helps to find out more about a KDE installation.

; [[Development/Tools/Using kfmclient|Driving Konqueror From Scripts - kfmclient]]
: kfmclient is a small tool to communicate with Konqueror.

;[[Development/Tools/Using kconf_update|Updating User Configuration Files - kconf_update]]
: kconf_update is a tool designed to update config files.

;[[Development/Tools/apidox|Generating apidox]]
: tools that help develop and generate API documentation for your code.

;[[Development/Tools/Automoc4|Automoc4]]
: This is a helper tool needed to build KDE4. It automatically generates moc-files.

;[[Development/Tools/svnmerge.py|svnmerge.py]]
: This tool helps keeping track of merges between different SVN branches

== Quality Assurance ==

; Continuous Building - Dashboard
: [http://developer.kde.org/~dirk/dashboard/ all kde modules on Dirk's dashboard]
: [http://winkde.org/pub/kde/ports/win32/dashboard/ some kde oftware on win32 dashboard]
: [http://public.kitware.com/dashboard.php?name=kde kdelibs on kitware]

; [http://englishbreakfastnetwork.org/ English Breakfast Network] - Static Analysis
: [http://www.englishbreakfastnetwork.org/krazy/ Krazy ] - Code Analysis, [[Development/Tutorials/Code_Checking|Usage Tutorial]]
: [http://www.englishbreakfastnetwork.org/apidocs/ APIDOX] - API Documentation Statistics
: [http://www.englishbreakfastnetwork.org/sanitizer/ Sanitizer] - DocBook Checker
: [http://www.englishbreakfastnetwork.org/usability/ Usability Checks]

User:Santa

2009-03-15T23:36:09Z

Santa: New page: I'm a noob who is just getting in touch with KDE programming and community. Thank you for be patient and careful with my job. If you can't find me in #kde-bugs, don't hesitate to mail me:...

I'm a noob who is just getting in touch with KDE programming and community. Thank you for be patient and careful with my job.

If you can't find me in #kde-bugs, don't hesitate to mail me:
panfaust (at) gmail.com

Contribute/Bugsquad/BugDays/KMailDay3

2009-03-15T22:59:58Z

Santa: /* KMail Bug Firewall catch-up */

==Introduction==

This is the page for KMailDay3 which takes place on Sunday, March 15th 2009, but feel free to start early. The aim of this bug day is to organize as many of the KMail bugs as possible, identifying duplicate bug reports and already fixed bugs. Our targets for triage are bugs listed in [http://bugs.kde.org bugs.kde.org] under the product kmail.

==Requirements==
You don't need any programming experience to help out with Triaging, but you will need a recent version of KMail, either svn trunk or a recent release (eg. KDE 4.2.1). Information on setting up KDE from trunk can be [http://techbase.kde.org/Getting_Started found here]. If you're having trouble installing KDE, feel free to drop by on #kde-bugs early to get some help.

==General information==
* [http://techbase.kde.org/Contribute/Bugsquad This page] has useful information on how to not mis-mark bugs. In particular, "duplicates are hard". Generally we don't want to claim things are duplicates when they aren't. Make sure you get '''approval from a developer''' before you mark something a duplicate. We don't want to create more work for the developers!
* Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. (You can even join now!)

==Preparations==
First of all, put your name and the version of KMail you are testing with into the Sign-in section. Then read the descriptions of the various sections to file bugs in carefully.

==Junior Jobs==

KMail is in search for bugs which are easy enough to fix for someone just starting out developing for KDE or KMail. Those kinds of bugs are called "Junior Jobs". If you think a bug sounds really easy to fix so it might qualify as a junior job, please put it in the "Junior Job Proposals" section. They will later be checked by the KMail developers if they really fit the scheme. In case a developer is around, you might as well ask him right away.

==Workflow==
# Select one of the batches of bugs you'd like to do and pick it by putting your name into the appropriate column.
# Execute the query to get the list of bugs and go through the bugs one by one.
## Read the bug description and the comments carefully and try to reproduce the bug.
## Post a comment on bugzilla explaining what you found out. Be sure to also put the version of KMail you are testing with in the comment.
## Put the bug into the appropriate section and describe your findings here as well (eg. "Can't reproduce any longer" or "This bug is still reproducible for me"). If there's something special about a bug, you can prepend a little label like eg. '''crash'''. Please mark every bug with your IRC nickname. You can easily do that by appending <nowiki>~~~</nowiki>.
## Check if the bug's Version field is set properly. The version field for KMail bugs should always contain the last KMail version the bug is/was reproducible with. If the bug is no longer reproducible and it's unclear which version the bug last appeared in, please set it to the version you '''think''' it last happened.
## Check if the bug's component is set correctly. It will be of great help when checking for duplicates (eg. comparing similar bugreports in the "Disconnected IMAP" component). If you lack permissions to change the component or are unsure about it, please put the bugs in the "needs component change" section along with a comment.
## Check if the bug might qualify as a "Junior Job". If so, please put it in the "Junior Job Proposal" section.
## Mark the bug as triaged by adding the '''triaged''' keyword on the bug. Again if you lack the permissions to do so, additionally put it in the "Needs triaged keyword" section.
# If you're done with your batch, pick another one and start from the top :-)

===Testcases===
Some bugs might have documents that expose the bugs attached, for some bugs you might be able to create data that shows the buggy behaviour. In both cases we have to add the '''testcase''' keyword. If you lack permissions to do so, additionally add the bug to the "Needs testcase keyword" section.

===Unclear===
If something has no clear instructions on how to reproduce it, or has little useful information, add a comment asking the reporter for more detail. Then list it in the [[#Bugs_awaiting_feedback|bugs awaiting feedback]] section. Be polite, we want to be nice to our bug reporters!

===Is it a big bug?===
Prioritizing is good. We're especially interested in problems that result in dataloss. Let's keep track of them.

===Double Check!===
'''Please list bugs here to get a second opinion before making the change in bugzilla. This also gives a record of what we've done for the developers to check.'''

===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 use the tag <s>...</s> to mark a bug as done <s>like this</s>.

==Hints==
* You can edit single sections of this page if you you check '''Enable section editing via edit links''' in your [[Special:Preferences|TechBase Preferences]].
* Sometimes you might encounter '''edit conflicts''' if several people are working on the wiki page at once. We can mostly avoid those by keeping notes of the bugs we encounter in a text editor and file several of them later at once (don't forget to save).

{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).}}

==Common Bugs==

There are some bugs which are commonly reported several times. If you found such a bug (or think you did), you can put it here:

===Message list related===

* {{bug|142609}} - Column sizes aren't saved
* {{bug|187217}} - Can't change column order, column order isn't saved
* {{bug|181794}} - Message list contains a dotted "tree line" even in flat view
* {{bug|178402}} - Configured custom fonts aren't used

===Account loss===

There should be plenty of bugs which are related to loosing accounts or settings (either on upgrade or on crash). If you find one of them, put them here.

* {{bug|174940}} - Account loss on upgrade and crash.

==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 beta2 if you're using that):

{|
|-
!IRC Nickname !! KMail version used for testing
|-
|[[User:Lemma|Lemma]]||svn trunk r939483 ||
|-
|[[User:jtamate|jtamate]]|| 4.2.65 (KDE 4.3 >= 20090226) ||
|-
|[[User:Dtritscher|dtritscher]]|| 4.2.1 ||
|-
|[[User:Brot|Brot]]|| gentoo-ebuilds 4.2.1 ||
|-
|[[User:Santa|santa_]]|| debian experimental packages (4.2.1) ||
|-
|[[User:DarioAndres|Dario_Andres]]|| svn rev. 939600 + Qt4.5+patches-936035 ||
|-
|[[User:Blauzahl|Blauzahl]]|| svn kdepim r939529 + Qt4.5 patches-935726 ||
|-
|}

==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 month's bugs you are working on to avoid duplication of effort.

If you have to leave before you can finish your batch, please put the last bug you triaged as well as if you're going to finish triaging in the table so others will know where you left off.

{{Warning| With these more recent bugs, if the report has been looked at by a developer (i.e. they cc'd themself or commented on it or posted a patch), and it seems like the issue is fixed, BUT the developer didn't close it, make sure the bug really can be closed. Often it can't.}}

===KMail Bug Firewall catch-up===

We've been checking incoming bugs for KMail for a while now. Newly filed bugs are assigned to bugsquad-triage@kde.org, checked by us and reassigned/forwarded to the developers if there was enough information and the bug was not a duplicate. This section lists the bugs which are still assigned to bugsquad-triage and thus are either rather new or need some more work before they can be passed on. We should start with those.

{{Tip|All of the Bug Firewall bugs' assignees have been set to the default assignee for KMail once they're handled by us. If you lack the permissions to do so, please put them in the "Needs assignee changed" section.}}

Information mostly for people organizing:
* The template query for Bug Firewall bugs is [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= this one].
* Check for [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= untriaged bugs].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || [[User:Lemma|Lemma]] || Starting || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=174755&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=176689 Query]
|-
| 2 || 10 || [[User:Dtritscher|dtritscher]] || Done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=176855&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=177792 Query]
|-
| 3 || 10 || [[User:Dtritscher|dtritscher]] || Working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=179095&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=179980 Query]
|-
| 4 || 10 ||[[User:Blauzahl|Blauzahl]] ||working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=179991&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=180374 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=180465&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=180955 Query]
|-
| 6 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=181065&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=181435 Query]
|-
| 7 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=181610&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=182209 Query]
|-
| 8 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=182212&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=182785 Query]
|-
| 9 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=182834&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=183276 Query]
|-
| 10 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=183280&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=183850 Query]
|-
| 11 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=183874&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=184325 Query]
|-
| 12 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=184377&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=184989 Query]
|-
| 13 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=185068&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=185331 Query]
|-
| 14 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=185390&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=185546 Query]
|-
| 15 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=185576&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=185821 Query]
|-
| 16 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=185838&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=186217 Query]
|-
| 17 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=186218&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=186500 Query]
|-
| 18 || 10 || [[User:Santa|santa_]] || Done, except 186522 || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=186501&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=186699 Query]
|-
| 19 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=186704&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=187078 Query]
|-
| 20 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=187108&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=1 Query]
|}
(Total bugs: 193)

===Other batches===
Information mostly for people organizing:
* The template query for other batches is [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Bug+Number this one].
* The query contains bugs filed in 2008.

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || [[User:jtamate|jtamate]] || still pending 155895 and 155910 || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=155025&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=155911 Query]
|-
| 2 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=155976&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=158081 Query]
|-
| 3 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=158134&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=159220 Query]
|-
| 4 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=159295&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=160216 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=160223&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=160961 Query]
|-
| 6 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=160967&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=161524 Query]
|-
| 7 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=161527&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=161707 Query]
|-
| 8 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=161728&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=162284 Query]
|-
| 9 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=162313&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=162840 Query]
|-
| 10 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=162900&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=163408 Query]
|-
| 11 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=163413&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=164449 Query]
|-
| 12 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=164549&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=165390 Query]
|-
| 13 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=165389&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=166079 Query]
|-
| 14 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=166149&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=167069 Query]
|-
| 15 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=167187&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=168359 Query]
|-
| 16 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=168493&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=169093 Query]
|-
| 17 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=169131&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=169494 Query]
|-
| 18 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=169513&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=170068 Query]
|-
| 19 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=170075&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=170308 Query]
|-
| 20 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=170378&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=170941 Query]
|}
(Total bugs: 200)

== Bugs that need changes that require permissions ==
If you put a bug into this section, please be sure you additionally put it into the appropriate '''Completed Bugs''' section.

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as TRIAGED}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as TESTCASE}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs needing version field changed}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs needing component field changed}}

== Special interest bugs ==

{{:Contribute/Bugsquad/BugDays/KMailDay3/High Profile}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Junior Job Proposals}}

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

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as RESOLVED}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs with test-cases}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs with step-by-step instructions}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as INVALID}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as DUPLICATE}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs that should be WISHES}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs needing users with particular setups}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Non english locales}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs needing attention from KMail developers}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs awaiting feedback}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs that you cant do}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs not related to KMail}}

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

2009-03-15T22:39:45Z

Santa: /* Bugs that you can't do */

===Bugs that you can't do===
If you have bugs in your batch that you can't do, and no-one has been able to help you with on IRC, please list them here for someone else to have a look at.

*[[Bug|186502]] It seems unreproducible, probably a developer needs the ~/.kde4/share/apps/kmail/imap file from the reporter. [[User:Santa|Santa]]

*[[Bug|186536]] I don't have 50k+ messages, so I try to reproduce the bug copying a dummy message pressing Crtl+Alt+C and keeping pressed Crtl+Alt+V, but I get a crash. [[User:Santa|Santa]] 22:39, 15 March 2009 (UTC)

Contribute/Bugsquad/BugDays/KMailDay3/Bugs awaiting feedback

2009-03-15T22:29:00Z

Santa: /* Bugs awaiting feedback */

===Bugs awaiting feedback===
Some bugs are hard to reproduce because the reporter left out some explanation you'd need. In that case we have no other means but to request some more information. Bugs for which feedback from the reporter has been requested should be put here. They should be revisited in 30 days to see if there's any response. If there's feedback

'''Feedback should only be requested for bugs if you have tried and failed to reproduce them or if the report contains insufficient information to try and reproduce the bug. Requesting feedback for a bug should be seen as a last resort only.'''

*[[Bug|155119]] Unable to reproduce, but asking the user if he still suffers it, as the bug is about losing information. [[User:Jtamate|Jtamate]]
*[[Bug|177405]] Unclear how to set up kmail to produce described behaviour, asked reporter for more detailed instructions. [[User:Dtritscher|dtritscher]] 16:38, 15 March 2009 (UTC)
*[[Bug|186695]] Unuseful backtrace, reporter has stripped binaries for kdepim. [[User:Santa|Santa]] 20:13, 15 March 2009 (UTC)
*[[Bug|186551]] I've requested an example to reporter. [[User:Santa|Santa]] 22:29, 15 March 2009 (UTC)

Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as TRIAGED

2009-03-15T21:36:44Z

Santa: /* Bugs to be marked as TRIAGED */

===Bugs to be marked as TRIAGED===
Bugs that need the '''triaged''' keyword adding to them should be listed here.

*[[Bug|186515]] This bug is still reproducible for me with kmail 1.11.1 [[User:Santa|Santa]] 17:24, 15 March 2009 (UTC)

*[[Bug|186698]] This bug is still reproducible for me with kmail 1.11.1 [[User:Santa|Santa]] 17:50, 15 March 2009 (UTC)

*[[Bug|186524]] This bug is reproducible for me (but not exactly in the same way) with kmail 1.11.1 [[User:Santa|Santa]] 19:41, 15 March 2009 (UTC)

*[[Bug|186529]] Should be reassigned to kdepim-bugs@kde.org, but I don't have permissions. [[User:Santa|Santa]] 21:36, 15 March 2009 (UTC)

Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as TRIAGED

2009-03-15T21:35:54Z

Santa: /* Bugs to be marked as TRIAGED */

Contribute/Bugsquad/BugDays/KMailDay3/Bugs needing component field changed

2009-03-15T21:14:00Z

Santa: /* Bugs needing component field changed */

===Bugs needing component field changed===
If a bug can be categorized better by changing its component field but you lack the permission to do it, please put the bug here.

*[[Bug|186674]] Probably isn't kmail fault. I've tested with kmail/kontact from kde 4.2.1 but in a kde 3 environment and I can't reproduce the bug. [[User:Santa|Santa]] 21:14, 15 March 2009 (UTC)

Contribute/Bugsquad/BugDays/KMailDay3/Bugs awaiting feedback

2009-03-15T20:13:14Z

Santa: /* Bugs awaiting feedback */

Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as TRIAGED

2009-03-15T19:43:21Z

Santa: /* Bugs to be marked as TRIAGED */

Contribute/Bugsquad/BugDays/KMailDay3/Bugs with step-by-step instructions

2009-03-15T19:42:15Z

Santa: /* Bugs with step-by-step instructions */

===Bugs with step-by-step instructions===
If the bug has proper step-by-step instructions to reproduce the bug it should go here. Actually most reproducible bugs should end up in this section.
* [[Bug|177020]] Reproducible with kmail 1.11.1 [[User:Dtritscher|dtritscher]] 12:11, 15 March 2009 (UTC)
* [[Bug|177492]] Could reproduce with kmail 1.11.1 [[User:Dtritscher|dtritscher]] 16:11, 15 March 2009 (UTC)
* [[Bug|177619]] Could reproduce with kmail 1.11.1 [[User:Dtritscher|dtritscher]] 16:20, 15 March 2009 (UTC)
* [[Bug|186698]] Could reproduce with kmail 1.11.1 [[User:Santa|Santa]] 18:03, 15 March 2009 (UTC)
*[[Bug|186524]] This bug is reproducible for me (but not exactly in the same way) with kmail 1.11.1 [[User:Santa|Santa]] 19:42, 15 March 2009 (UTC)

Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as TRIAGED

2009-03-15T19:41:18Z

Santa: /* Bugs to be marked as TRIAGED */

===Bugs to be marked as TRIAGED===
Bugs that need the '''triaged''' keyword adding to them should be listed here.

*[[Bug|186515]] This bug is still reproducible for me with kmail 1.11.1 [[User:Santa|Santa]] 17:24, 15 March 2009 (UTC)

*[[Bug|186698]] This bug is still reproducible for me with kmail 1.11.1 [[User:Santa|Santa]] 17:50, 15 March 2009 (UTC)

*[[Bug|186524]] This bug is reproducible for me (but not excatly in the same way) with kmail 1.11.1 [[User:Santa|Santa]] 19:41, 15 March 2009 (UTC)

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

2009-03-15T18:27:07Z

Santa: /* Bugs that you can't do */

Contribute/Bugsquad/BugDays/KMailDay3/Bugs with step-by-step instructions

2009-03-15T18:03:49Z

Santa: /* Bugs with step-by-step instructions */

Contribute/Bugsquad/BugDays/KMailDay3

2009-03-15T17:54:05Z

Santa: /* KMail Bug Firewall catch-up */

==Introduction==

This is the page for KMailDay3 which takes place on Sunday, March 15th 2009, but feel free to start early. The aim of this bug day is to organize as many of the KMail bugs as possible, identifying duplicate bug reports and already fixed bugs. Our targets for triage are bugs listed in [http://bugs.kde.org bugs.kde.org] under the product kmail.

==Requirements==
You don't need any programming experience to help out with Triaging, but you will need a recent version of KMail, either svn trunk or a recent release (eg. KDE 4.2.1). Information on setting up KDE from trunk can be [http://techbase.kde.org/Getting_Started found here]. If you're having trouble installing KDE, feel free to drop by on #kde-bugs early to get some help.

==General information==
* [http://techbase.kde.org/Contribute/Bugsquad This page] has useful information on how to not mis-mark bugs. In particular, "duplicates are hard". Generally we don't want to claim things are duplicates when they aren't. Make sure you get '''approval from a developer''' before you mark something a duplicate. We don't want to create more work for the developers!
* Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. (You can even join now!)

==Preparations==
First of all, put your name and the version of KMail you are testing with into the Sign-in section. Then read the descriptions of the various sections to file bugs in carefully.

==Junior Jobs==

KMail is in search for bugs which are easy enough to fix for someone just starting out developing for KDE or KMail. Those kinds of bugs are called "Junior Jobs". If you think a bug sounds really easy to fix so it might qualify as a junior job, please put it in the "Junior Job Proposals" section. They will later be checked by the KMail developers if they really fit the scheme. In case a developer is around, you might as well ask him right away.

==Workflow==
# Select one of the batches of bugs you'd like to do and pick it by putting your name into the appropriate column.
# Execute the query to get the list of bugs and go through the bugs one by one.
## Read the bug description and the comments carefully and try to reproduce the bug.
## Post a comment on bugzilla explaining what you found out. Be sure to also put the version of KMail you are testing with in the comment.
## Put the bug into the appropriate section and describe your findings here as well (eg. "Can't reproduce any longer" or "This bug is still reproducible for me"). If there's something special about a bug, you can prepend a little label like eg. '''crash'''. Please mark every bug with your IRC nickname. You can easily do that by appending <nowiki>~~~</nowiki>.
## Check if the bug's Version field is set properly. The version field for KMail bugs should always contain the last KMail version the bug is/was reproducible with. If the bug is no longer reproducible and it's unclear which version the bug last appeared in, please set it to the version you '''think''' it last happened.
## Check if the bug's component is set correctly. It will be of great help when checking for duplicates (eg. comparing similar bugreports in the "Disconnected IMAP" component). If you lack permissions to change the component or are unsure about it, please put the bugs in the "needs component change" section along with a comment.
## Check if the bug might qualify as a "Junior Job". If so, please put it in the "Junior Job Proposal" section.
## Mark the bug as triaged by adding the '''triaged''' keyword on the bug. Again if you lack the permissions to do so, additionally put it in the "Needs triaged keyword" section.
# If you're done with your batch, pick another one and start from the top :-)

===Testcases===
Some bugs might have documents that expose the bugs attached, for some bugs you might be able to create data that shows the buggy behaviour. In both cases we have to add the '''testcase''' keyword. If you lack permissions to do so, additionally add the bug to the "Needs testcase keyword" section.

===Unclear===
If something has no clear instructions on how to reproduce it, or has little useful information, add a comment asking the reporter for more detail. Then list it in the [[#Bugs_awaiting_feedback|bugs awaiting feedback]] section. Be polite, we want to be nice to our bug reporters!

===Is it a big bug?===
Prioritizing is good. We're especially interested in problems that result in dataloss. Let's keep track of them.

===Double Check!===
'''Please list bugs here to get a second opinion before making the change in bugzilla. This also gives a record of what we've done for the developers to check.'''

===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 use the tag <s>...</s> to mark a bug as done <s>like this</s>.

==Hints==
* You can edit single sections of this page if you you check '''Enable section editing via edit links''' in your [[Special:Preferences|TechBase Preferences]].
* Sometimes you might encounter '''edit conflicts''' if several people are working on the wiki page at once. We can mostly avoid those by keeping notes of the bugs we encounter in a text editor and file several of them later at once (don't forget to save).

{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).}}

==Common Bugs==

There are some bugs which are commonly reported several times. If you found such a bug (or think you did), you can put it here:

===Message list related===

* {{bug|142609}} - Column sizes aren't saved
* {{bug|187217}} - Can't change column order, column order isn't saved
* {{bug|181794}} - Message list contains a dotted "tree line" even in flat view
* {{bug|178402}} - Configured custom fonts aren't used

===Account loss===

There should be plenty of bugs which are related to loosing accounts or settings (either on upgrade or on crash). If you find one of them, put them here.

* {{bug|174940}} - Account loss on upgrade and crash.

==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 beta2 if you're using that):

{|
|-
!IRC Nickname !! KMail version used for testing
|-
|[[User:Lemma|Lemma]]||svn trunk r939483 ||
|-
|[[User:jtamate|jtamate]]|| 4.2.65 (KDE 4.3 >= 20090226) ||
|-
|[[User:Dtritscher|dtritscher]]|| 4.2.1 ||
|-
|[[User:Brot|Brot]]|| gentoo-ebuilds 4.2.1 ||
|-
|[[User:Santa|santa_]]|| debian experimental packages (4.2.1) ||
-
|[[User:DarioAndres|Dario_Andres]]|| svn rev. 939600 + Qt4.5+patches-936035 ||
|}

==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 month's bugs you are working on to avoid duplication of effort.

If you have to leave before you can finish your batch, please put the last bug you triaged as well as if you're going to finish triaging in the table so others will know where you left off.

{{Warning| With these more recent bugs, if the report has been looked at by a developer (i.e. they cc'd themself or commented on it or posted a patch), and it seems like the issue is fixed, BUT the developer didn't close it, make sure the bug really can be closed. Often it can't.}}

===KMail Bug Firewall catch-up===

We've been checking incoming bugs for KMail for a while now. Newly filed bugs are assigned to bugsquad-triage@kde.org, checked by us and reassigned/forwarded to the developers if there was enough information and the bug was not a duplicate. This section lists the bugs which are still assigned to bugsquad-triage and thus are either rather new or need some more work before they can be passed on. We should start with those.

{{Tip|All of the Bug Firewall bugs' assignees have been set to the default assignee for KMail once they're handled by us. If you lack the permissions to do so, please put them in the "Needs assignee changed" section.}}

Information mostly for people organizing:
* The template query for Bug Firewall bugs is [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= this one].
* Check for [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= untriaged bugs].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || [[User:Lemma|Lemma]] || Starting || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=174755&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=176689 Query]
|-
| 2 || 10 || [[User:Dtritscher|dtritscher]] || Done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=176855&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=177792 Query]
|-
| 3 || 10 || [[User:Dtritscher|dtritscher]] || Working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=179095&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=179980 Query]
|-
| 4 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=179991&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=180374 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=180465&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=180955 Query]
|-
| 6 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=181065&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=181435 Query]
|-
| 7 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=181610&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=182209 Query]
|-
| 8 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=182212&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=182785 Query]
|-
| 9 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=182834&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=183276 Query]
|-
| 10 || 10 || [[User:DarioAndres|Dario_Andres]] || Working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=183280&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=183850 Query]
|-
| 11 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=183874&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=184325 Query]
|-
| 12 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=184377&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=184989 Query]
|-
| 13 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=185068&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=185331 Query]
|-
| 14 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=185390&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=185546 Query]
|-
| 15 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=185576&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=185821 Query]
|-
| 16 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=185838&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=186217 Query]
|-
| 17 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=186218&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=186500 Query]
|-
| 18 || 10 || [[User:Santa|santa_]] || Working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=186501&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=186699 Query]
|-
| 19 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=186704&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=187078 Query]
|-
| 20 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=187108&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=1 Query]
|}
(Total bugs: 193)

===Other batches===
Information mostly for people organizing:
* The template query for other batches is [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Bug+Number this one].
* The query contains bugs filed in 2008.

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || [[User:jtamate|jtamate]] || still pending 155895 and 155910 || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=155025&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=155911 Query]
|-
| 2 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=155976&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=158081 Query]
|-
| 3 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=158134&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=159220 Query]
|-
| 4 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=159295&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=160216 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=160223&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=160961 Query]
|-
| 6 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=160967&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=161524 Query]
|-
| 7 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=161527&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=161707 Query]
|-
| 8 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=161728&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=162284 Query]
|-
| 9 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=162313&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=162840 Query]
|-
| 10 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=162900&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=163408 Query]
|-
| 11 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=163413&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=164449 Query]
|-
| 12 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=164549&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=165390 Query]
|-
| 13 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=165389&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=166079 Query]
|-
| 14 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=166149&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=167069 Query]
|-
| 15 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=167187&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=168359 Query]
|-
| 16 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=168493&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=169093 Query]
|-
| 17 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=169131&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=169494 Query]
|-
| 18 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=169513&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=170068 Query]
|-
| 19 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=170075&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=170308 Query]
|-
| 20 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=170378&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=170941 Query]
|}
(Total bugs: 200)

== Bugs that need changes that require permissions ==
If you put a bug into this section, please be sure you additionally put it into the appropriate '''Completed Bugs''' section.

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as TRIAGED}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as TESTCASE}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs needing version field changed}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs needing component field changed}}

== Special interest bugs ==

{{:Contribute/Bugsquad/BugDays/KMailDay3/High Profile}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Junior Job Proposals}}

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

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as RESOLVED}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs with test-cases}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs with step-by-step instructions}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as INVALID}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as DUPLICATE}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs that should be WISHES}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs needing users with particular setups}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Non english locales}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs needing attention from KMail developers}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs awaiting feedback}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs that you cant do}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs not related to KMail}}

Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as TRIAGED

2009-03-15T17:50:52Z

Santa: /* Bugs to be marked as TRIAGED */

Contribute/Bugsquad/BugDays/KMailDay3/Bugs that should be WISHES

2009-03-15T17:29:00Z

Santa: /* Bugs that should be WISHES */

===Bugs that should be WISHES===
Sometimes there are bugs that are actually wishlist items. If you think a bug is not really a bug please put it here.

*[[Bug|186515]] This bug is still reproducible for me with kmail 1.11.1 [[User:Santa|Santa]] 17:26, 15 March 2009 (UTC)

Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as TRIAGED

2009-03-15T17:27:55Z

Santa: /* Bugs to be marked as TRIAGED */

Contribute/Bugsquad/BugDays/KMailDay3/Bugs that should be WISHES

2009-03-15T17:26:03Z

Santa: /* Bugs that should be WISHES */

Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as TRIAGED

2009-03-15T17:24:05Z

Santa: /* Bugs to be marked as TRIAGED */

===Bugs to be marked as TRIAGED===
Bugs that need the '''triaged''' keyword adding to them should be listed here.

*[[Bug|186515]] This bug is still reproducible for me. [[User:Santa|Santa]] 17:24, 15 March 2009 (UTC)

Contribute/Bugsquad/BugDays/KMailDay3

2009-03-15T13:55:13Z

Santa: /* KMail Bug Firewall catch-up */

==Introduction==

This is the page for KMailDay3 which takes place on Sunday, March 15th 2009, but feel free to start early. The aim of this bug day is to organize as many of the KMail bugs as possible, identifying duplicate bug reports and already fixed bugs. Our targets for triage are bugs listed in [http://bugs.kde.org bugs.kde.org] under the product kmail.

==Requirements==
You don't need any programming experience to help out with Triaging, but you will need a recent version of KMail, either svn trunk or a recent release (eg. KDE 4.2.1). Information on setting up KDE from trunk can be [http://techbase.kde.org/Getting_Started found here]. If you're having trouble installing KDE, feel free to drop by on #kde-bugs early to get some help.

==General information==
* [http://techbase.kde.org/Contribute/Bugsquad This page] has useful information on how to not mis-mark bugs. In particular, "duplicates are hard". Generally we don't want to claim things are duplicates when they aren't. Make sure you get '''approval from a developer''' before you mark something a duplicate. We don't want to create more work for the developers!
* Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. (You can even join now!)

==Preparations==
First of all, put your name and the version of KMail you are testing with into the Sign-in section. Then read the descriptions of the various sections to file bugs in carefully.

==Junior Jobs==

KMail is in search for bugs which are easy enough to fix for someone just starting out developing for KDE or KMail. Those kinds of bugs are called "Junior Jobs". If you think a bug sounds really easy to fix so it might qualify as a junior job, please put it in the "Junior Job Proposals" section. They will later be checked by the KMail developers if they really fit the scheme. In case a developer is around, you might as well ask him right away.

==Workflow==
# Select one of the batches of bugs you'd like to do and pick it by putting your name into the appropriate column.
# Execute the query to get the list of bugs and go through the bugs one by one.
## Read the bug description and the comments carefully and try to reproduce the bug.
## Post a comment on bugzilla explaining what you found out. Be sure to also put the version of KMail you are testing with in the comment.
## Put the bug into the appropriate section and describe your findings here as well (eg. "Can't reproduce any longer" or "This bug is still reproducible for me"). If there's something special about a bug, you can prepend a little label like eg. '''crash'''. Please mark every bug with your IRC nickname. You can easily do that by appending <nowiki>~~~</nowiki>.
## Check if the bug's Version field is set properly. The version field for KMail bugs should always contain the last KMail version the bug is/was reproducible with. If the bug is no longer reproducible and it's unclear which version the bug last appeared in, please set it to the version you '''think''' it last happened.
## Check if the bug's component is set correctly. It will be of great help when checking for duplicates (eg. comparing similar bugreports in the "Disconnected IMAP" component). If you lack permissions to change the component or are unsure about it, please put the bugs in the "needs component change" section along with a comment.
## Check if the bug might qualify as a "Junior Job". If so, please put it in the "Junior Job Proposal" section.
## Mark the bug as triaged by adding the '''triaged''' keyword on the bug. Again if you lack the permissions to do so, additionally put it in the "Needs triaged keyword" section.
# If you're done with your batch, pick another one and start from the top :-)

===Testcases===
Some bugs might have documents that expose the bugs attached, for some bugs you might be able to create data that shows the buggy behaviour. In both cases we have to add the '''testcase''' keyword. If you lack permissions to do so, additionally add the bug to the "Needs testcase keyword" section.

===Unclear===
If something has no clear instructions on how to reproduce it, or has little useful information, add a comment asking the reporter for more detail. Then list it in the [[#Bugs_awaiting_feedback|bugs awaiting feedback]] section. Be polite, we want to be nice to our bug reporters!

===Is it a big bug?===
Prioritizing is good. We're especially interested in problems that result in dataloss. Let's keep track of them.

===Double Check!===
'''Please list bugs here to get a second opinion before making the change in bugzilla. This also gives a record of what we've done for the developers to check.'''

===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 use the tag <s>...</s> to mark a bug as done <s>like this</s>.

==Hints==
* You can edit single sections of this page if you you check '''Enable section editing via edit links''' in your [[Special:Preferences|TechBase Preferences]].
* Sometimes you might encounter '''edit conflicts''' if several people are working on the wiki page at once. We can mostly avoid those by keeping notes of the bugs we encounter in a text editor and file several of them later at once (don't forget to save).

{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).}}

==Common Bugs==

There are some bugs which are commonly reported several times. If you found such a bug (or think you did), you can put it here:

===Message list related===

* {{bug|142609}} - Column sizes aren't saved
* {{bug|187217}} - Can't change column order, column order isn't saved
* {{bug|181794}} - Message list contains a dotted "tree line" even in flat view
* {{bug|178402}} - Configured custom fonts aren't used

===Account loss===

There should be plenty of bugs which are related to loosing accounts or settings (either on upgrade or on crash). If you find one of them, put them here.

* {{bug|174940}} - Account loss on upgrade and crash.

==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 beta2 if you're using that):

{|
|-
!IRC Nickname !! KMail version used for testing
|-
|[[User:Lemma|Lemma]]||svn trunk r939483 ||
|-
|[[User:jtamate|jtamate]]|| 4.2.65 (KDE 4.3 >= 20090226) ||
|-
|[[User:Dtritscher|dtritscher]]|| 4.2.1 ||
|-
|[[User:Brot|Brot]]|| gentoo-ebuilds 4.2.1 ||
|-
|[[User:Santa|santa_]]|| debian experimental packages (4.2.1) ||
|}

==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 month's bugs you are working on to avoid duplication of effort.

If you have to leave before you can finish your batch, please put the last bug you triaged as well as if you're going to finish triaging in the table so others will know where you left off.

{{Warning| With these more recent bugs, if the report has been looked at by a developer (i.e. they cc'd themself or commented on it or posted a patch), and it seems like the issue is fixed, BUT the developer didn't close it, make sure the bug really can be closed. Often it can't.}}

===KMail Bug Firewall catch-up===

We've been checking incoming bugs for KMail for a while now. Newly filed bugs are assigned to bugsquad-triage@kde.org, checked by us and reassigned/forwarded to the developers if there was enough information and the bug was not a duplicate. This section lists the bugs which are still assigned to bugsquad-triage and thus are either rather new or need some more work before they can be passed on. We should start with those.

{{Tip|All of the Bug Firewall bugs' assignees have been set to the default assignee for KMail once they're handled by us. If you lack the permissions to do so, please put them in the "Needs assignee changed" section.}}

Information mostly for people organizing:
* The template query for Bug Firewall bugs is [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= this one].
* Check for [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= untriaged bugs].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || [[User:Lemma|Lemma]] || Starting || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=174755&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=176689 Query]
|-
| 2 || 10 || [[User:Dtritscher|dtritscher]] || Starting || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=176855&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=177792 Query]
|-
| 3 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=179095&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=179980 Query]
|-
| 4 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=179991&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=180374 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=180465&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=180955 Query]
|-
| 6 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=181065&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=181435 Query]
|-
| 7 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=181610&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=182209 Query]
|-
| 8 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=182212&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=182785 Query]
|-
| 9 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=182834&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=183276 Query]
|-
| 10 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=183280&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=183850 Query]
|-
| 11 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=183874&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=184325 Query]
|-
| 12 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=184377&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=184989 Query]
|-
| 13 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=185068&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=185331 Query]
|-
| 14 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=185390&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=185546 Query]
|-
| 15 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=185576&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=185821 Query]
|-
| 16 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=185838&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=186217 Query]
|-
| 17 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=186218&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=186500 Query]
|-
| 18 || 10 || [[User:Santa|santa_]] || Starting || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=186501&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=186699 Query]
|-
| 19 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=186704&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=187078 Query]
|-
| 20 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=187108&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=1 Query]
|}
(Total bugs: 193)

===Other batches===
Information mostly for people organizing:
* The template query for other batches is [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Bug+Number this one].
* The query contains bugs filed in 2008.

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || [[User:jtamate|jtamate]] || still pending 155895 and 155910 || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=155025&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=155911 Query]
|-
| 2 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=155976&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=158081 Query]
|-
| 3 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=158134&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=159220 Query]
|-
| 4 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=159295&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=160216 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=160223&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=160961 Query]
|-
| 6 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=160967&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=161524 Query]
|-
| 7 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=161527&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=161707 Query]
|-
| 8 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=161728&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=162284 Query]
|-
| 9 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=162313&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=162840 Query]
|-
| 10 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=162900&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=163408 Query]
|-
| 11 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=163413&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=164449 Query]
|-
| 12 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=164549&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=165390 Query]
|-
| 13 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=165389&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=166079 Query]
|-
| 14 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=166149&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=167069 Query]
|-
| 15 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=167187&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=168359 Query]
|-
| 16 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=168493&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=169093 Query]
|-
| 17 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=169131&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=169494 Query]
|-
| 18 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=169513&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=170068 Query]
|-
| 19 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=170075&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=170308 Query]
|-
| 20 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=170378&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=170941 Query]
|}
(Total bugs: 200)

== Bugs that need changes that require permissions ==
If you put a bug into this section, please be sure you additionally put it into the appropriate '''Completed Bugs''' section.

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as TRIAGED}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as TESTCASE}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs needing version field changed}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs needing component field changed}}

== Special interest bugs ==

{{:Contribute/Bugsquad/BugDays/KMailDay3/High Profile}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Junior Job Proposals}}

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

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as RESOLVED}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs with test-cases}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs with step-by-step instructions}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as INVALID}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as DUPLICATE}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs that should be WISHES}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs needing users with particular setups}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Non english locales}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs needing attention from KMail developers}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs awaiting feedback}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs that you cant do}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs not related to KMail}}

Contribute/Bugsquad/BugDays/KMailDay3

2009-03-15T13:50:54Z

Santa: /* Sign-in */

==Introduction==

This is the page for KMailDay3 which takes place on Sunday, March 15th 2009, but feel free to start early. The aim of this bug day is to organize as many of the KMail bugs as possible, identifying duplicate bug reports and already fixed bugs. Our targets for triage are bugs listed in [http://bugs.kde.org bugs.kde.org] under the product kmail.

==Requirements==
You don't need any programming experience to help out with Triaging, but you will need a recent version of KMail, either svn trunk or a recent release (eg. KDE 4.2.1). Information on setting up KDE from trunk can be [http://techbase.kde.org/Getting_Started found here]. If you're having trouble installing KDE, feel free to drop by on #kde-bugs early to get some help.

==General information==
* [http://techbase.kde.org/Contribute/Bugsquad This page] has useful information on how to not mis-mark bugs. In particular, "duplicates are hard". Generally we don't want to claim things are duplicates when they aren't. Make sure you get '''approval from a developer''' before you mark something a duplicate. We don't want to create more work for the developers!
* Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. (You can even join now!)

==Preparations==
First of all, put your name and the version of KMail you are testing with into the Sign-in section. Then read the descriptions of the various sections to file bugs in carefully.

==Junior Jobs==

KMail is in search for bugs which are easy enough to fix for someone just starting out developing for KDE or KMail. Those kinds of bugs are called "Junior Jobs". If you think a bug sounds really easy to fix so it might qualify as a junior job, please put it in the "Junior Job Proposals" section. They will later be checked by the KMail developers if they really fit the scheme. In case a developer is around, you might as well ask him right away.

==Workflow==
# Select one of the batches of bugs you'd like to do and pick it by putting your name into the appropriate column.
# Execute the query to get the list of bugs and go through the bugs one by one.
## Read the bug description and the comments carefully and try to reproduce the bug.
## Post a comment on bugzilla explaining what you found out. Be sure to also put the version of KMail you are testing with in the comment.
## Put the bug into the appropriate section and describe your findings here as well (eg. "Can't reproduce any longer" or "This bug is still reproducible for me"). If there's something special about a bug, you can prepend a little label like eg. '''crash'''. Please mark every bug with your IRC nickname. You can easily do that by appending <nowiki>~~~</nowiki>.
## Check if the bug's Version field is set properly. The version field for KMail bugs should always contain the last KMail version the bug is/was reproducible with. If the bug is no longer reproducible and it's unclear which version the bug last appeared in, please set it to the version you '''think''' it last happened.
## Check if the bug's component is set correctly. It will be of great help when checking for duplicates (eg. comparing similar bugreports in the "Disconnected IMAP" component). If you lack permissions to change the component or are unsure about it, please put the bugs in the "needs component change" section along with a comment.
## Check if the bug might qualify as a "Junior Job". If so, please put it in the "Junior Job Proposal" section.
## Mark the bug as triaged by adding the '''triaged''' keyword on the bug. Again if you lack the permissions to do so, additionally put it in the "Needs triaged keyword" section.
# If you're done with your batch, pick another one and start from the top :-)

===Testcases===
Some bugs might have documents that expose the bugs attached, for some bugs you might be able to create data that shows the buggy behaviour. In both cases we have to add the '''testcase''' keyword. If you lack permissions to do so, additionally add the bug to the "Needs testcase keyword" section.

===Unclear===
If something has no clear instructions on how to reproduce it, or has little useful information, add a comment asking the reporter for more detail. Then list it in the [[#Bugs_awaiting_feedback|bugs awaiting feedback]] section. Be polite, we want to be nice to our bug reporters!

===Is it a big bug?===
Prioritizing is good. We're especially interested in problems that result in dataloss. Let's keep track of them.

===Double Check!===
'''Please list bugs here to get a second opinion before making the change in bugzilla. This also gives a record of what we've done for the developers to check.'''

===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 use the tag <s>...</s> to mark a bug as done <s>like this</s>.

==Hints==
* You can edit single sections of this page if you you check '''Enable section editing via edit links''' in your [[Special:Preferences|TechBase Preferences]].
* Sometimes you might encounter '''edit conflicts''' if several people are working on the wiki page at once. We can mostly avoid those by keeping notes of the bugs we encounter in a text editor and file several of them later at once (don't forget to save).

{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).}}

==Common Bugs==

There are some bugs which are commonly reported several times. If you found such a bug (or think you did), you can put it here:

===Message list related===

* {{bug|142609}} - Column sizes aren't saved
* {{bug|187217}} - Can't change column order, column order isn't saved
* {{bug|181794}} - Message list contains a dotted "tree line" even in flat view
* {{bug|178402}} - Configured custom fonts aren't used

===Account loss===

There should be plenty of bugs which are related to loosing accounts or settings (either on upgrade or on crash). If you find one of them, put them here.

* {{bug|174940}} - Account loss on upgrade and crash.

==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 beta2 if you're using that):

{|
|-
!IRC Nickname !! KMail version used for testing
|-
|[[User:Lemma|Lemma]]||svn trunk r939483 ||
|-
|[[User:jtamate|jtamate]]|| 4.2.65 (KDE 4.3 >= 20090226) ||
|-
|[[User:Dtritscher|dtritscher]]|| 4.2.1 ||
|-
|[[User:Brot|Brot]]|| gentoo-ebuilds 4.2.1 ||
|-
|[[User:Santa|santa_]]|| debian experimental packages (4.2.1) ||
|}

==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 month's bugs you are working on to avoid duplication of effort.

If you have to leave before you can finish your batch, please put the last bug you triaged as well as if you're going to finish triaging in the table so others will know where you left off.

{{Warning| With these more recent bugs, if the report has been looked at by a developer (i.e. they cc'd themself or commented on it or posted a patch), and it seems like the issue is fixed, BUT the developer didn't close it, make sure the bug really can be closed. Often it can't.}}

===KMail Bug Firewall catch-up===

We've been checking incoming bugs for KMail for a while now. Newly filed bugs are assigned to bugsquad-triage@kde.org, checked by us and reassigned/forwarded to the developers if there was enough information and the bug was not a duplicate. This section lists the bugs which are still assigned to bugsquad-triage and thus are either rather new or need some more work before they can be passed on. We should start with those.

{{Tip|All of the Bug Firewall bugs' assignees have been set to the default assignee for KMail once they're handled by us. If you lack the permissions to do so, please put them in the "Needs assignee changed" section.}}

Information mostly for people organizing:
* The template query for Bug Firewall bugs is [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= this one].
* Check for [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= untriaged bugs].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || [[User:Lemma|Lemma]] || Starting || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=174755&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=176689 Query]
|-
| 2 || 10 || [[User:Dtritscher|dtritscher]] || Starting || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=176855&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=177792 Query]
|-
| 3 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=179095&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=179980 Query]
|-
| 4 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=179991&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=180374 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=180465&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=180955 Query]
|-
| 6 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=181065&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=181435 Query]
|-
| 7 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=181610&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=182209 Query]
|-
| 8 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=182212&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=182785 Query]
|-
| 9 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=182834&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=183276 Query]
|-
| 10 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=183280&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=183850 Query]
|-
| 11 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=183874&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=184325 Query]
|-
| 12 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=184377&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=184989 Query]
|-
| 13 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=185068&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=185331 Query]
|-
| 14 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=185390&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=185546 Query]
|-
| 15 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=185576&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=185821 Query]
|-
| 16 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=185838&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=186217 Query]
|-
| 17 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=186218&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=186500 Query]
|-
| 18 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=186501&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=186699 Query]
|-
| 19 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=186704&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=187078 Query]
|-
| 20 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=bugsquad-triage&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=187108&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=1 Query]
|}
(Total bugs: 193)

===Other batches===
Information mostly for people organizing:
* The template query for other batches is [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-01&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Bug+Number this one].
* The query contains bugs filed in 2008.

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 10 || [[User:jtamate|jtamate]] || still pending 155895 and 155910 || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=155025&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=155911 Query]
|-
| 2 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=155976&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=158081 Query]
|-
| 3 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=158134&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=159220 Query]
|-
| 4 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=159295&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=160216 Query]
|-
| 5 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=160223&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=160961 Query]
|-
| 6 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=160967&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=161524 Query]
|-
| 7 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=161527&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=161707 Query]
|-
| 8 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=161728&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=162284 Query]
|-
| 9 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=162313&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=162840 Query]
|-
| 10 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=162900&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=163408 Query]
|-
| 11 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=163413&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=164449 Query]
|-
| 12 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=164549&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=165390 Query]
|-
| 13 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=165389&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=166079 Query]
|-
| 14 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=166149&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=167069 Query]
|-
| 15 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=167187&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=168359 Query]
|-
| 16 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=168493&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=169093 Query]
|-
| 17 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=169131&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=169494 Query]
|-
| 18 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=169513&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=170068 Query]
|-
| 19 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=170075&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=170308 Query]
|-
| 20 || 10 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kmail&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=170378&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=170941 Query]
|}
(Total bugs: 200)

== Bugs that need changes that require permissions ==
If you put a bug into this section, please be sure you additionally put it into the appropriate '''Completed Bugs''' section.

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as TRIAGED}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as TESTCASE}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs needing version field changed}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs needing component field changed}}

== Special interest bugs ==

{{:Contribute/Bugsquad/BugDays/KMailDay3/High Profile}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Junior Job Proposals}}

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

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as RESOLVED}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs with test-cases}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs with step-by-step instructions}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as INVALID}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs to be marked as DUPLICATE}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs that should be WISHES}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs needing users with particular setups}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Non english locales}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs needing attention from KMail developers}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs awaiting feedback}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs that you cant do}}

{{:Contribute/Bugsquad/BugDays/KMailDay3/Bugs not related to KMail}}