Quoted from Rarehero:Enough with this "just because it isn't good doesn't mean it isn't unfinished"
Total cop out
totally not a cop out. The development team writes out a list of goals and rules. They then implement those. When they are all implemented, they are "done". The fact that we think the original list of rules sucks does not make the code unfinished. It makes the code suck. They are very different things.
To complete unfinished code, stern would have allocated internal resources to do this. As they plan projects and timelines, they will have a list of goals and allocate time to complete them. Once those goals are completed, the dev team moves onto something else. If those goals have been met but the product sucks, then stern has to reallocate resources to finish it or say that they're not going to.
Lyman chooses to work on this on his own time. Lonnie doesn't.
It feels like the current dev cycle at stern (like with xmen) overlaps the shipping date. And resources are still allocated onto the project a few months after initial ship. This allows us, the community, an opportunity to make suggestions. Since the team is still working, if the devs like the suggestions, they may implement some of these ideas. They wouldn't need permission to work on the code - they already still are.
In case of being dropped finished code, this would indicate to me that the dev cycle ends on shipping. Those dev resources would move onto another project. If there are community suggestions, stern would have to cease development of the new project and move resources back to the previous project. If those suggestions aren't critical they definitely wouldn't be done.
It feels like this is what happened on transformers.