I did this yesterday with my Fly Away Rabbit game. I'd tried it once or twice before and really the frustration of trying to figure out what all had changed and update it was kind of discouraging. I updated from 0.82 to 0.99.5 though.

Anyway, I found it a lot easier after I started developing another app for 0.99.5 and figured out how to do everything with the new API first. Of course you can learn it as you go it just may take longer to make the changes.

MikeSz's points are great. definitely keep those in mind.

What I did was create a whole new project using 0.99.5. My project used cocos2d + box2d so I used the box2d template. Then I copied all my source files and graphics from the old Fly Away Rabbit project into the new one. I compiled and started picking off the errors one by one. I found that find and replace on the project helped out a lot. Like

Find: Layer Replace: CCLayer
Find AtlasSprite Replace: CCSpriteBatchNode

it will find all the things that need to be changed... just make sure you're only making changes into the files that you wrote and not the cocos2d files.

Just a little advice, hope it helps. Took me about 5 hours to go through the 104 classes in my Classes folder. And it's incredible how much faster my 0.99.5 version is compared to the currently released 0.82 version

You should also read the release notes for all versions (including point releases) to learn about any deprecatated and/or removed APIs.

Ahh you should also check the latest Cocosdenshion source since it has changed a little.

Thanks to all. :-)
As per my game scope, I have used the cocos2d, chipmunk, cocosdension lib.

I did this with a rather small project this thursday and other than adding CC everywhere:

1) transformAnchor changed to anchorPoint
2) transformAnchor used to be set in pixels, now it's from (0,0) (lower left) to (1,1) - top right
3) setR:x G:y B:z changes to setColor:ccc3(x,y,z)
4) Director covertCoordinate - convertToGL
5) add and getByTag change to addChild and getChildByTag
6) do:(Action*) became runAction
7) Label - CCLabelTTF
8) If you created animations using animationWithName:(NSString*) delay:(int) images:@"image1", @"image2", @"image3", nil (nil to terminate) - change that to:
a) create a new animation - animationWithName: delay:
b) add frames one by one - addFrameWithFilename:
9) Back in the old days a single Node could have been attached to many parents (for example we used same background Sprite across many scenes). this is no longer the case and will crash on NSAssert
10) cpVect is CGPoint now, cpv is ccp (this one is freaking annoying as it's everywhere)
11) Currently CCDirector is attached to the window in a completely different way

There's more of course but those cover the basics

Overall it took me 2 hours to go through the whole game, fix all the issues and mount the new CCDirector using EAGL layer

Have fun ;)

Hi Pravin, just as ddeaco says it depends on the scale of the project.
Most times i just replace the cocos2d sources and then manually solve ll those errors from the new naming conventions or classes that changed.

I had to do this a while back. Depends really on the scale ofyour app. I just replaced the cocos2D lib and worked through the thousands of errors using text replace mainly.

If I was to do it again I would probably download the latest version and then make a template project and add your old class files one by one starting with what runs first eg the main menu. Then check it for errors when that bit works add the next. If your using chipmunk there were a few changes in that you will have to look out for as well.

It basically takes a while but isn't super hard.

David
_______
Follow me on -
http://www.twitter.com/david__deacon
http://www.twitter.com/iceflamegames

Hi,
Thanks in advance.
I have developed the app before 1.8 yrs back using cocos2d 0.7 version.
Now to support retina display feature for iPhone 4 I need to upgrade cocos2d to 0.99.5.
I'll try but it's too complicated. Please suggest the steps to upgrade it.
Please help