On Fri, Jan 23, 2009 at 1:34 AM, Stephan Aßmus <superstippi@xxxxxx> wrote: > How about compiling a list of bugs that we would each consider a suitable > test when fixed? > > I think fixing a bug, unless it's a really trivial one, is a pretty good > test. It > > * makes sure you have setup a build env, > * involves you with the community and the other devs when you questions, > * involves you with the community during feedback for the bug, > * tests your coding skills and ability to follow the coding guide lines, > * tests your ability to find your way in the existing code base. Might I recommend that they fix info? In r28911, at least, info crashes whenever it's started up. It's a problem that should be easy to fix (Maybe?), but it won't matter to the average desktop user (and the more seasoned UNIX users).