Release cycles after 2.0
I'm not sure if there is already a discussion going on about this, but I would like to express my opinion and encourage others to do the same.
As everyone can see, there have been tons of great improvements since development for 2.0 started three years ago. The problem is that only power users could see what was going on by testing the nightlies. For your regular "I use what's released" user, it looked as if nothing happened for three (or at least two since 1.3) years.
By following the old mantra "release early, release often", MuseScore might become more visible. With the manpower you have, a release cycle like the 2.x Linux kernels might be a reasonable idea. This way, bugfixes and small improvements could go into 2.0.x, while the cool (and possibly unstable) stuff goes to 2.1.x until it is considered stable enough to be called 2.2.0 and so on.
I'm curious what others think about this...