Ha, I had a feeling that if I wasn’t quick enough to reply myself, somebody would come along and repeat my old mantra that Dorico development isn’t a democracy, which is something I say to make a particular point, rather than because I’m some kind of despotic authoritarian: on the contrary, I think it’s very important that Dorico’s development is driven by consensus, especially internal consensus among the team with immediate responsibility for specifying, designing, implementing and testing the software, but also in terms of the overall alignment of what its users, in the aggregate, want to see.
However, any kind of attempt to reduce to a single, ranked list of requests the complex processes and considerations that go into how we decide what to work on and when would be reductive to the point of being misleading. And a negative side effect would be to provide a nice, centralised place for our competitors to go and get a very good idea of what we are working on. There’s plenty of, shall we say, inspiration being drawn from Dorico by other developers in our little niche already without giving those developers the additional advantage of telling them what we are doing before it has been released.