Revoice first or include it with 3.2?
Hey everyone, Kerstyn and I were talking about the possibility that we could just tackle the revoice first and release it as sort of a mini-update before 3.2.
Then 3.2 would be released at a later date, without the revoice and just with the new content.
The pros of this approach are that Kerstyn and I can finally complete the revoice sooner (likely within this month), but the cons of this approach are that all new content for 3.2, including the custom names will have to wait until a bit later (mid-late October).
What do you think of this idea?
Comments (5)
I would say get the revoice out of the way sooner rather than later, that way you can focus on making some sweet, new content!
Agreed, focusing on the revoice is the sound strategy.
Completing the remaining revoice work is the more organic option, IMO. That way you're free to focus entirely on all new content for the next release and others beyond it.
For the people who missed the original deadline for custom names in 3.2. Would this mean they would be in 3.2 or would we still have to wait for 3.3
If Kerstyn and I decide to do the revoice first then the deadline would naturally be extended :) That means 3.3 requests would be transferred over to 3.2.