On Fri, May 11, 2012 at 7:00 PM, Anne-Marie Mahfouf <[email protected]> wrote: > Hi all, > > Here is I hope a summary of the tasks we're aiming for the next 4.9 release. > Current wiki pages: > http://community.kde.org/Getinvolved/Testing > http://community.kde.org/Getinvolved/Testing/Brainstorming > > Don't forget that you can use https://trello.com/kdetesting (ask Myriam or > me for account) > > 1) On a wiki page > List of plasmoids to test: David Edmundson > (http://community.kde.org/Plasma/Tasks for known problems with applets) > 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.
http://community.kde.org/Getinvolved/Testing/Beta/Plasma#Beta_Testing_Plasmoids Just about to email Plasma, to let them know of the plans, and to try and get a definitive list of the rewritten plasmoids > > List of apps to test: > > Pairs > Rocs > kcm which changed? Can I confirm that I'm not tasked with sorting out the testing on these apps, just the plasmoids. Last email made it look like I was, and I don't know what Rocs/Pairs are, so I'm not best to it. > > 2) Make bugs.kde.org ready for testers: annma submitted a sysadmin bugreport > https://bugs.kde.org/show_bug.cgi?id=299703 > Explain this to testers in the bigzilla training stage > > 3) Write Dot Article http://quality.notes.kde.org/1 opened to everyone > should be published the 29th May > Write blogs from May 30th and afterwards > > 4) Bugzilla training: who? > http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports > https://wiki.kubuntu.org/Kubuntu/Bugs/Reporting (has some Kubuntu specific > parts, but the topic "how to write good reports" is still valid) > http://aseigo.blogspot.co.uk/2009/01/bugskdeorg.html > http://itscommonsensestupid.blogspot.co.uk/2008/07/tips-to-write-good-bug-report.html > Martin's blogs > http://blog.martin-graesslin.com/blog/2012/04/blog-series-bugs-kde-org-for-developers/ > Myriam's blog: > http://blogs.fsfe.org/myriam/2011/10/when-is-a-bug-report-useful/ > > 5) Contact distributions: annma => setup a wiki page with informations about > this beata packages and how to install. > Current situation: > Slackware: > The packages will be obtainable at http://alien.slackbook.org/ktown/ > The instructions for usage will be posted on > http://alien.slackbook.org/blog/ > Arch Linux: > A dedicated [kde-unstable] repository. This repo only > contains KDE/Calligra beta releases (and their unstable deps); when the > stable > version is out, the packages are removed. > Installation steps are at: > https://wiki.archlinux.org/index.php/KDE#Official_kde-unstable > and https://wiki.archlinux.org/index.php/DeveloperWiki:KDE#Users > Fedora: there is an unofficial kde-unstable/kde-testing and > a kde-stable repo maintained by Rex Dieter - the place where the newest > bits come for already released stuff. But Fedora Rawhide is always the > first place for all builds. > Gentoo: provides scm versions (ebuilds) for master/trunk & stable branch, > betas > and rc's in an extra repository (overlay). Detailed install instructions can > be found here: > http://www.gentoo.org/proj/en/desktop/kde/kde4-guide.xml > > 6) IRC based "bug squashing days": 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) > To do in coordination with the current bugsquad (write them a mail). Who? > https://mail.kde.org/mailman/listinfo/bugsquad > > 7) Logo for the Quality Team? > For blogs Can we ask Eugene? > > 8) Rewards for Testers? > Good incentive and would make people feel part of the community. > See > http://community.kde.org/Getinvolved/Testing/Brainstorming#Personalized_Thank_You_Letter > and > http://community.kde.org/Getinvolved/Testing/Brainstorming#Competition_For_Best_Bug_Reporters > > > > > _______________________________________________ > Kde-testing mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/kde-testing > _______________________________________________ Kde-testing mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-testing
