July 2006


Well, we said CMake rocks, but after the time we have used it, we have generally come to like it. So far it has provided our escape we wanted, and given us more flexibility and ease of build system modification. A generally good experience all round you could say.

Well thats all very nice, technically, but this post is just a big thank you to the CMake team that have helped me with the migration task, and in more recent times, quick fixes into CMake, and fixes into our CMake setup. I had made some mistakes initially and it wasn’t until this week that I had time to track it down as discrepancies between building here and on other devs’ machines didn’t make sense. You know… clean checkout, clean build of CMake and Scribus… builds fine here. Same clean versions on another box… splat. In the end, it was a mistake in my code and the CMake guys spent the time to find it… simply outstanding support. Another vote from me goes their way.

Two days ago I filed issue #4000 on Scribus’s bug tracker. 🙂
I also wanted to file #3000 but mrdocs beat me on that this January.
Ugh? Another 1000 bugs in merely six months??

Yep. This shows that the Scribus project is not only active at the development front but also has people who care about its quality and keep track of issues. Fortunately, most of these 1000 new bugs are already closed:

scribus-bugs-cummulative
Another diagram shows that the majority of issues are feature requests or minor issues:


Currently there are only 116 unresolved issues with severity major, block or crash. So what happens to issues which get resolved? While we also have resolutions like “no change required” and “won’t fix”, most issues get fixed:

Which shows we are not only working hard, but we’ve also got the statistics to prove it! 😉 For those who are interested in more statistics, they should check out the “Summary” and “Advanced summary” sections at http://bugs.scribus.net.
Keep on feeding us those bugs, we love it!

/Andreas