Anderton
The difference with the new model is that bug fixes won't stop past a certain point as they did in the past, but are ongoing, although possibly at a reduced rate. If development slows down, the team can go back into the "bugs archive" and fix longstanding bugs; there's been evidence of that in the past several releases.
I see the bugs in 3 categories:
1) Regression bugs.
2) Really old bugs that never got fixed up to X3E (there appears to be quite a backlog). Many one could regard as 'legacy'.
3) The rest.
Obviously (1) should and is getting priority. I would hope to see a bigger push for (2). It appears the main reason why we aren't is because of regression bugs coming from new features. Most just seem to hang around.
I had hoped one developer would be set aside for nothing but bug fixing until the event horizon is met (clearly I must have sad fanasies!). :)
Well let's just see if almost all the track view bugs and workflow issues get quashed with the audio enhancements coming up. That would send a more positive message IMHO.