I’ve developed my game with cocos 2.0.1 on iOS and Android. Now my boss gave me a task to port that game to Blackberry platform.
I found support for Blackberry in 2.0.4 release. But in the same time I found a lot of differences in API between 2.0.1 and 2.0.4 - most of these in create() methods: in 2.0.4 you’ve removed a lot of create(param) methods without any deprecation and replaces them with createWithXXX(param).
CCArray::create(unsigned int capacity) ~~> CCArray::createWithCapacity
CCSprite::create~~> CCSprite::createWithSpriteFrame(CCSpriteFrame *pSpriteFrame)
I’m sure I’ll find more along my porting efforts.
Is it good policy for the project? I found this very bad practice to break API in such way within the same 2.0.x series of releases, without any deprecation period.
Other open source projects I know (and in some of them I was involved to) have good deprecation practice, at least I don’t expect them to seriously change API between minor releases of the project.
Why did you do so, guys? Why?