Get Involved/Quality/Brainstorming: Difference between revisions
mNo edit summary |
Mgraesslin (talk | contribs) No edit summary |
||
| Line 6: | Line 6: | ||
Ask Anne-Marie or Myriam for help if needed. | Ask Anne-Marie or Myriam for help if needed. | ||
= Daily Live-CD/VM image in beta phase = | |||
== Rational == | |||
Our current test approach is handing source packages to the distros, waiting for them to have packages and hope that users will install them. Distros often try building the next version for the first time with the first beta release and they need too long. When the packages hit the user the next beta is already in preparation. New reported bugs are very often already fixed and just create overhead. | |||
Distros provide the packages in a way that it replaces the stable packages, so users who don't want to use beta quality packages cannot help during beta testing. | |||
Providing a daily live-cd/vm image could help here: users can just use a virtual machine to perform testing or download the CD and give it a try. As it is a daily build we don't run into the issue that it is already outdated when the user tries it. | |||
For daily images project neon of Kubuntu could be used or susestudio. Of course maybe sysadmins could setup something to build the image directly from Jenkins. | |||
--[[User:Mgraesslin|Mgraesslin]] 18:37, 6 April 2012 (BST) | |||
= Beta Tester need special group in bugtracker = | = Beta Tester need special group in bugtracker = | ||
Revision as of 17:37, 6 April 2012
This temporary page is aimed at brainstorming.
Please move things to be done to the collaborative tool here: https://trello.com/kdetesting
Ask Anne-Marie or Myriam for help if needed.
Daily Live-CD/VM image in beta phase
Rational
Our current test approach is handing source packages to the distros, waiting for them to have packages and hope that users will install them. Distros often try building the next version for the first time with the first beta release and they need too long. When the packages hit the user the next beta is already in preparation. New reported bugs are very often already fixed and just create overhead.
Distros provide the packages in a way that it replaces the stable packages, so users who don't want to use beta quality packages cannot help during beta testing.
Providing a daily live-cd/vm image could help here: users can just use a virtual machine to perform testing or download the CD and give it a try. As it is a daily build we don't run into the issue that it is already outdated when the user tries it.
For daily images project neon of Kubuntu could be used or susestudio. Of course maybe sysadmins could setup something to build the image directly from Jenkins. --Mgraesslin 18:37, 6 April 2012 (BST)
Beta Tester need special group in bugtracker
Rational
Developers need to know that a bug has been created by a dedicated beta tester. Why is that important? If the developers know that the reporter is capable of producing high quality reports it is not needed to do the usual developer-user interaction but it can be assumed that the bug is valid. --Mgraesslin 19:38, 5 April 2012 (BST)
Personalized Thank You Letter
Proposal
Every user who reported e.g. ten high quality bug reports during the beta testing which got fixed before the release receive a personalized Thank You Letter signed by a prominent KDE developer. --Mgraesslin 19:38, 5 April 2012 (BST)
Competition For Best Bug Reporters
Proposal
The users who report most bugs during the beta test which get fixed before the release can win a prize. Of course the bug reports have to be of high quality. --Mgraesslin 19:38, 5 April 2012 (BST)