<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi all,<br>
<br>
Here is I hope a summary of the tasks we're aiming for the next 4.9
release.<br>
<meta http-equiv="CONTENT-TYPE" content="text/html;
charset=ISO-8859-1">
Current wiki pages:
<br>
<a href="http://community.kde.org/Getinvolved/Testing">http://community.kde.org/Getinvolved/Testing</a>
<br>
<a href="http://community.kde.org/Getinvolved/Testing/Brainstorming">http://community.kde.org/Getinvolved/Testing/Brainstorming</a>
<br>
<br>
Don't forget that you can use <a
href="https://trello.com/kdetesting">https://trello.com/kdetesting</a>
(ask Myriam or me for account)<br>
<title></title>
<meta name="GENERATOR" content="LibreOffice 3.4 (Linux)">
<style type="text/css">
<!--
@page { margin: 0.79in }
P { margin-bottom: 0.08in }
A:link { so-language: zxx }
--></style><br>
<meta http-equiv="CONTENT-TYPE" content="text/html;
charset=ISO-8859-1">
<u>1) On a wiki page</u>
<br>
List of plasmoids to test: <b>David
Edmundson</b>
<br>
(<a href="http://community.kde.org/Plasma/Tasks">http://community.kde.org/Plasma/Tasks</a>
for known problems with applets)
<br>
Test with default theme, with Oxygen
theme, various positions (on the desktop, putting in a horizontal
panel, a vertical panel), size (default start size, resize to
minimum size), test all configuration settings, test right click
mouse actions if relevant, GHNS if relevant, test specific areas for
each applet.<br>
<br>
List of apps to test:
<ul>
<li>Pairs </li>
<li>Rocs </li>
<li>kcm which changed?
</li>
</ul>
2) <u>Make bugs.kde.org ready for
tester</u>s: <b>annma </b><span style="font-weight: normal">submitted
a
sysadmin bugreport</span>
<br>
<a href="https://bugs.kde.org/show_bug.cgi?id=299703">https://bugs.kde.org/show_bug.cgi?id=299703</a>
<br>
Explain this to testers in the bigzilla
training stage
<br>
<br>
3) <u>Write Dot Article</u>
<a href="http://quality.notes.kde.org/1">http://quality.notes.kde.org/1</a>
<b>opened to everyone</b>
<br>
should be published the 29<sup>th</sup>
May
<br>
<u>Write blogs</u> from May 30<sup>th</sup>
and afterwards
<br>
<br>
4) <u>Bugzilla training</u>: who?
<br>
<a
href="http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports">http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports</a>
<br>
<a href="https://wiki.kubuntu.org/Kubuntu/Bugs/Reporting">https://wiki.kubuntu.org/Kubuntu/Bugs/Reporting</a>
(has some Kubuntu specific parts, but the topic "how to write
good reports" is still valid)
<br>
<a href="http://aseigo.blogspot.co.uk/2009/01/bugskdeorg.html">http://aseigo.blogspot.co.uk/2009/01/bugskdeorg.html</a>
<br>
<a
href="http://itscommonsensestupid.blogspot.co.uk/2008/07/tips-to-write-good-bug-report.html">http://itscommonsensestupid.blogspot.co.uk/2008/07/tips-to-write-good-bug-report.html</a>
<br>
Martin's blogs
<a
href="http://blog.martin-graesslin.com/blog/2012/04/blog-series-bugs-kde-org-for-developers/">http://blog.martin-graesslin.com/blog/2012/04/blog-series-bugs-kde-org-for-developers/</a>
<br>
Myriam's blog:
<a
href="http://blogs.fsfe.org/myriam/2011/10/when-is-a-bug-report-useful/">http://blogs.fsfe.org/myriam/2011/10/when-is-a-bug-report-useful/</a>
<br>
<br>
5) <u>Contact distributions</u>: <b>annma</b>
=> setup a wiki page with informations about this beata packages
and how to install. <br>
Current situation:
<br>
<u>Slackware</u>:<br>
The packages will
be obtainable at <a href="http://alien.slackbook.org/ktown/">http://alien.slackbook.org/ktown/</a>
<br>
The instructions for usage will be posted on
<a href="http://alien.slackbook.org/blog/">http://alien.slackbook.org/blog/</a>
<br>
<u>Arch Linux</u>: <br>
A dedicated [kde-unstable] repository.
This repo only <br>
contains KDE/Calligra beta releases
(and their unstable deps); when the stable <br>
version is out, the packages are
removed.
<br>
Installation steps are at: <br>
<a
href="https://wiki.archlinux.org/index.php/KDE#Official_kde-unstable">https://wiki.archlinux.org/index.php/KDE#Official_kde-unstable</a>
<br>
and
<a
href="https://wiki.archlinux.org/index.php/DeveloperWiki:KDE#Users">https://wiki.archlinux.org/index.php/DeveloperWiki:KDE#Users</a>
<br>
<u>Fedora:</u> there is an unofficial
kde-unstable/kde-testing and <br>
a kde-stable repo maintained by Rex
Dieter - the place where the newest
<br>
bits come for already released stuff.
But Fedora Rawhide is always the
<br>
first place for all builds.
<br>
<u>Gentoo</u>: provides scm versions
(ebuilds) for master/trunk & stable branch, betas <br>
and rc's in an extra repository
(overlay). Detailed install instructions can <br>
be found here:
<br>
<a href="http://www.gentoo.org/proj/en/desktop/kde/kde4-guide.xml">http://www.gentoo.org/proj/en/desktop/kde/kde4-guide.xml</a>
<br>
<br>
6) <u>IRC based "bug squashing
days"</u><span style="text-decoration: none">: </span>do we want
to propose some dates for that. I think we need to have people on
IRC
in #kde-quality and #kde-bugs on May 29th, 30th and maybe we can set
the next week-end as formal "bug week-end" (that would be 2
and 3rd June)
<br>
To do in coordination with the current
bugsquad (write them a mail). Who?
<br>
<a href="https://mail.kde.org/mailman/listinfo/bugsquad">https://mail.kde.org/mailman/listinfo/bugsquad</a>
<br>
<br>
7) Logo for the Quality Team?
<br>
For blogs Can we ask Eugene?
<br>
<br>
8) Rewards for Testers?
<br>
Good incentive and would make people
feel part of the community.
<br>
See
<a
href="http://community.kde.org/Getinvolved/Testing/Brainstorming#Personalized_Thank_You_Letter">http://community.kde.org/Getinvolved/Testing/Brainstorming#Personalized_Thank_You_Letter</a>
<br>
and
<br>
<a
href="http://community.kde.org/Getinvolved/Testing/Brainstorming#Competition_For_Best_Bug_Reporters">http://community.kde.org/Getinvolved/Testing/Brainstorming#Competition_For_Best_Bug_Reporters</a>
<br>
<br>
<br>
<title></title>
<meta name="GENERATOR" content="LibreOffice 3.4 (Linux)">
<style type="text/css">
<!--
@page { margin: 0.79in }
P { margin-bottom: 0.08in }
A:link { so-language: zxx }
-->
</style><br>
</body>
</html>