Code-In a Big Success for Documentation
By Valorie Zimmermann:
Last week the students continued to work on our Handbook, and the tasks are progressing very nicely. Now that the Handbook tasks are almost finished, they are lending a hand for our next “Amarok Insider” (past issues available at
http://amarok.kde.org/Insider). It’s inspiring to work with these students, some of whom are very young, and yet are so smart, and work so hard. They have started hanging out in the #amarok and #rokymotion channel more, and getting to know some of our developers and helpful testers and users. I’ve set 39 tasks so far, and 25 are already completed! And most of my open tasks are claimed, so we’re doing very well.
Dealing with Regressions and Crashes
By Valorie Zimmermann:
Everyone has been working really hard on testing out our new features, and making sure that 2.4 is excellent! We’re collecting information about regressions and crashes to help in this effort. If you come across something which troubles you in 2.4 beta, please come into IRC, write to the Forum or list, or file a bug. We don’t see this as whining or complaining, but helping us make Amarok better! IRC is great if you can come in, because sometimes help or bug-fixing can take place on the spot! Quite inspiring to see our talented developers and the rest of the team in action.
Dealing with regressions and crashes is not quite as much fun as seeing new stuff get added to Amarok, but it is very important to a successful process. So, please help us out!
Bugs and Wishes
By Myriam Schweingruber:
Last week we have continued our bug-fixing work to get the next Amarok version out of the door. Amarok 2.4 is shaping up nicely. We have fixed a total of 98 bugs only this single week! There were of course a fair amount of duplicates, but the statistics are the following:
8 implemented wishes
33 fixed bugs, of which 14 were crashes
13 invalid reports
33 duplicate reports
3 upstream and 2 downstream reports
Two reports were pushed to later and four were closed as “WONTFIX”. Now, what does this mean? Well, most of the time either it is a wish that is out of the scope of Amarok, or it cannot be implemented within a reasonable amount of time by the developers.
Why so many duplicates then? Well, it is simply an indicator of a growing user base, since the more duplicates we get, the more users are willing to report their problems! Of course it would be nice to have the users check for duplicates first, but not everybody understands the system the first time around, and it up to us triagers to help them making better reports in the future