I just put Inscape to a little real-world usability test by drawing several diagrams. While there are many small interface improvements I could think up for myself, the biggest problem were bugs. More specifically, two kinds of bugs: the undo bugs and save bugs. You run into them very often. I don't think we can release 0.36 with them. I urge everyone to please go to the tracker and fix as many as you can. Some of them must be pretty simple.
On Tue, 25 Nov 2003, bulia byak wrote:
I just put Inscape to a little real-world usability test by drawing several diagrams. While there are many small interface improvements I could think up for myself, the biggest problem were bugs. More specifically, two kinds of bugs: the undo bugs and save bugs. You run into them very often. I don't think we can release 0.36 with them. I urge everyone to please go to the tracker and fix as many as you can. Some of them must be pretty simple.
Yes, this is an issue we'll need to hammer down prior to making a release.
But it isn't cause for alarm yet; this is normal for the development process we're using. Since so many of us are working directly on the codebase, it's going to get messy. This is why tracking, feature freezing and bug hunts are critical parts of the process. (This is also why modularity and testing frameworks are very important.)
It is also important that we always test out each other's code. It's very easy for us to focus on our own area of interest in the code, but if we're going to succeed as a team, we do best to take some time to review each other's work. Review is good for morale, good for quality, and good for knowledge-transfer.
So for right now, when anyone finds a bug, make sure it is listed in the bug tracker at an appropriate criticality ranking, so we can be sure we are not releasing Inkscape 0.36 with any critical bugs.
Bryce
participants (2)
-
Bryce Harrington
-
bulia byak