It seemed that the Dev team disbanded and became a one-person army part way through the process, after they had already started down a refactoring (i.e., redesigning the code, pipeline, content, etc.) path pretty heavily. So, I can understand that took a couple of months to try and settle, then the Dev mentioned having to shelve some ideas for better ones gleaned by the experience and has since been working on the actual story dev+content. So, longer than a three month window you might typically expect at the far end, but understandable to an extent - because some things were promised that they want to ensure are included. A mid-term deliverable of the new platform was offered more recently, btw (no new content though).
It's tough to know when to stop and ship it vs. adding in more, I figure. I would think that after things got stretched out from the refactoring and team downsizing, the desire to deliver ALOT in the next release as a way to make up for the additional time became the new priority.
But honestly, I feel delivering something sooner and then adding smaller updates at a quicker pace can be better in many cases - maybe this is one? I don't know, it may be that some timelines/paths needed rewrites to work better in the larger scope of things, but again I feel that such things could be handled by concentrating on a few areas of change at a time and catching up with old branches later. I tend to be a completist and like seeing a larger picture working properly, but have been trying to accept that some things I want to change might not happen at fully coordinated or even pacings of their individual parts- it's a tough habit to break.
