After 8 days since the KDE 4.9 first Beta was released, 93 bug reports were open or confirmed against this version and 31 from those are already fixed. A few bugs were also fixed without any report issued.
We have 2 new very active newcomers full of energy and doing a great job.
New applets are almost all tested (see http://community.kde.org/Getinvolved/Testing/Beta/Plasma) we now need to concentrate less on Plasma and more on applications.
Don't hesitate to join if your distribution provides the Beta (Beta 2 will be out really soon). Channel #kde-quality on IRC (Freenode) is a convenient way to get introduced and work with others. Developers also are welcome to join this channel!
If you report bugs, do not forget to set your KDE version in the "Version:" field. This should reflect the KDE version of the first reporter then the highest KDE version on which the bug was reproduced to ensure the report is always up-to-date.
Tuesday, June 12, 2012
Thursday, June 07, 2012
Testing KDE 4.9: status
Yesterday I indicated how one can participate to KDE 4.9 Beta 1 testing phase. There is indeed a Live CD available at http://susestudio.com/a/tAWYe6/kde-plasma-daily
We are prioritizing the testing of new applets, new applications and new features and we have functional tests ready to be used. Please read my previous post to learn more about this. Janek was the first person doing a functional test of the Now Playing applet and sending a report to the Quality mailing list. He opened 2 bug reports following his tests. Thanks a lot Janek!
Testers test and report bugs. Reporting good bugs is compulsory if we want devels to fix them. We need to make the developers focus on the most important bugs. Stating the KDE version in the "Version:" field in a bug report is compulsory. If you identify a regression, you can add the word "regression" in the "keywords" field. This will help targeting specific bug reports as a priority to be fixed.
I am pleased to report that some bugs have already been fixed and we triaged lots of bug reports, especially in Plasma. I'd like to thank all the users who take time to report bugs and who took time to answer our questions about older reports. We were pleased to see that lots of bug reporters care enough to help us having precise bug reports which will lead to better and quicker fixes.
The Quality Team will conduct a bugzilla training this week-end on IRC in #kde-bugs (freenode) (June 9th and 10th). We will also be available to help people wanting to be part in testing in #kde-quality. Do not hesitate to join if you can spare a bit of time for KDE. I also invite all developers to join this training in order to use bugzilla more efficiently!
We are prioritizing the testing of new applets, new applications and new features and we have functional tests ready to be used. Please read my previous post to learn more about this. Janek was the first person doing a functional test of the Now Playing applet and sending a report to the Quality mailing list. He opened 2 bug reports following his tests. Thanks a lot Janek!
Testers test and report bugs. Reporting good bugs is compulsory if we want devels to fix them. We need to make the developers focus on the most important bugs. Stating the KDE version in the "Version:" field in a bug report is compulsory. If you identify a regression, you can add the word "regression" in the "keywords" field. This will help targeting specific bug reports as a priority to be fixed.
I am pleased to report that some bugs have already been fixed and we triaged lots of bug reports, especially in Plasma. I'd like to thank all the users who take time to report bugs and who took time to answer our questions about older reports. We were pleased to see that lots of bug reporters care enough to help us having precise bug reports which will lead to better and quicker fixes.
The Quality Team will conduct a bugzilla training this week-end on IRC in #kde-bugs (freenode) (June 9th and 10th). We will also be available to help people wanting to be part in testing in #kde-quality. Do not hesitate to join if you can spare a bit of time for KDE. I also invite all developers to join this training in order to use bugzilla more efficiently!
Wednesday, June 06, 2012
Testing KDE 4.9 Beta1 (version 4.8.80)
As you may know, we recently set up a Quality and Testing team within KDE. We prepared
some wiki pages (http://community.kde.org/Getinvolved/Testing/Beta) and now that the Beta 1 is out,
several people already joined this Testing phase.
How can you get involved?
Install the Beta 1 from your distribution, most known distributions provide packages for it.
After that, you can choose two ways of testing:
- either use the release as you would normally and look for regressions, bugs, crashes,... Please report them to bugs.kde.org (try to search if the bug was already reported, for a quicker result you can ask on IRC, freenode, in #kde-bugs), do not forget to set up the version in your bug report as well as the precise stps to reproduce the bug. If it is a regression, explain how it was before.
- or choose a specific component to test in a more thorough way. We focus in priority on new additions to this release, on changed components and on new features. You can therefore test applets (http://community.kde.org/Getinvolved/Testing/Beta/Plasma) or test full programs (http://community.kde.org/Getinvolved/Testing/Beta/4.9Applications) or new features (http://community.kde.org/index.php?title=Getinvolved/Testing/Beta/AreasToTest). Copy the proposed tests in a text file and add a note like "works" or "OK" after testing each proposed feature. Then send your text to the Quality Team (kde-testing@kde.org) with your name or nickname. You can also extend those tests if you find other things to test, that will be useful in the future and also when we will move to more automated tests. I believe testing an applet does not require much time while testing a full application is more time demanding.
There is something to work on for everyone!
Testing does not require any specific knowledge: install the Beta and have a bugzilla account are the only requirements.
Please do not hesitate to join this effort and raise the quality of this release. Developers will then get batches of bugs to fix, priority will be given to regression and blockers. Several bugs already have been fixed!
IRC channels on freenode are #kde-quality and #kde-bugs
Mailing list is https://mail.kde.org/mailman/listinfo/kde-testing
How can you get involved?
Install the Beta 1 from your distribution, most known distributions provide packages for it.
After that, you can choose two ways of testing:
- either use the release as you would normally and look for regressions, bugs, crashes,... Please report them to bugs.kde.org (try to search if the bug was already reported, for a quicker result you can ask on IRC, freenode, in #kde-bugs), do not forget to set up the version in your bug report as well as the precise stps to reproduce the bug. If it is a regression, explain how it was before.
- or choose a specific component to test in a more thorough way. We focus in priority on new additions to this release, on changed components and on new features. You can therefore test applets (http://community.kde.org/Getinvolved/Testing/Beta/Plasma) or test full programs (http://community.kde.org/Getinvolved/Testing/Beta/4.9Applications) or new features (http://community.kde.org/index.php?title=Getinvolved/Testing/Beta/AreasToTest). Copy the proposed tests in a text file and add a note like "works" or "OK" after testing each proposed feature. Then send your text to the Quality Team (kde-testing@kde.org) with your name or nickname. You can also extend those tests if you find other things to test, that will be useful in the future and also when we will move to more automated tests. I believe testing an applet does not require much time while testing a full application is more time demanding.
There is something to work on for everyone!
Testing does not require any specific knowledge: install the Beta and have a bugzilla account are the only requirements.
Please do not hesitate to join this effort and raise the quality of this release. Developers will then get batches of bugs to fix, priority will be given to regression and blockers. Several bugs already have been fixed!
IRC channels on freenode are #kde-quality and #kde-bugs
Mailing list is https://mail.kde.org/mailman/listinfo/kde-testing
Subscribe to:
Posts (Atom)