Search
Goodies

Social Networks
Designs I Like
« Latest iPhone rumors summary | Main | Another Milestone: The waiting game »
Monday
May252009

Planning the next version, already

Now that my first application has been submitted to the App Store, I want to prepare for the next version. I want to know what you guys are doing. I want to know what do you do within Xcode:

  • Do you keep developing in the same code base ?
  • Are you creating a "new code branch" ?

Thanks for your input.

Reader Comments (4)

Your best bet is to create a "tag" in git or svn that marks the point at which you submitted the app to the app store. Then, if you need to push out emergency bugfixes before another proper release is ready, you can create a bugfix branch from that tag (and merge it back into the trunk after submitting the bugfix version to the app store).

I'd personally recommend git because of the ease of branching/merging, but svn will work too.

May 26, 2009 at 17:11 | Unregistered CommenterJarin Udom

Do you have any reference to GIT ou SVN ? So far, I managed to copy my Xcode project folder and named it after the version number of my application. So, If I need to go back, I can just open this old Xcode project, make any modifications then recompile and execute... Not sure to understand the real value of GIT or SVN....

May 27, 2009 at 12:09 | Unregistered CommenterJFMartin

This is your best bet right here:

http://pragprog.com/titles/tsgit/pragmatic-version-control-using-git

It's very well-written and in-depth.

May 27, 2009 at 16:10 | Unregistered CommenterJarin Udom

Seriously if you're not using version control you need to start immediately. It's akin to using a code editor that doesn't have an Undo function. Or like not doing backups. Or like having an email program that doesn't save old emails.

http://devreview.com/version-control-for-solo-developers/

May 27, 2009 at 16:14 | Unregistered CommenterJarin Udom

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>