Jason Slack-Moehrle wrote:
So is it smart to refactor and release a game with 3.0? I have been working on a game using 2.1.4 and am not planning to release for a few months. Ricardo said 3.0 is more stable than 2.1.4…When I try and upgrade to 3.0. I have a lot of trouble with selectors. For example in 2.1.4 I could do:
but in 3.0 I haven’t found an alternative that I can get to work for ‘(cocos2d::SEL_MenuHandler) &HUDForPlanting::plantBroccoli’
You want my advice? Release on the latest stable release, report all bugs and post any stability issues you find (for all our sakes!)
Ricardo also said “your code will compile with thousands of warnings” and “In a few months it will be stable, but in the meantime you should know that”alpha" means… well “alpha”, use it with caution, know the risks before using it."
The risks, if you are not aware, are unforeseen bugs, extended fix cycles, on going optimization and potential breaking API changes. That will let Ricardo and the 3.0 team move quickly.
Progress on 2.1.x will be slower because we are all fighting to keep our stable games stable — that means only changes that improve performance and fix bugs (as Ricardo indicates above.)
My advice is:
- Use what you are currently using if you are anywhere close to release.
- Trying to upgrade mid-project is often a bad plan.
- 2.1.x has been used for many successful games, just look at all those links!