Cabbits!

Update: After more thought, making a dev app and a live app is a good solution. It just doesn’t seem elegant.

I have searched the wiki and forums for a way to implement revision control but see no proper way to utilize revision control. Whether a developer is using SVN, Bazaar, CVS or some other system, managing their Dev environment separately from their Live environment is essential for evolving code.I’ve seen mention of Test Accounts in my search for an answer. However, after reading the documentation, I see this is useful solution for a Pre-Release application. The problem I’m worried about is once I let my app out into the wild. Bugs fixes and feature additions are going to be a part of any application development. Revision control helps to aid in an easy transition from version 1.0 to 1.x and eventually 2.0.

I currently use SVN to maintain my Dev and Live environments. It is kinda like my security blanket since I can break Dev and not affect Live users. My concern with developing a Facebook app is when I move from production to release. The best feasible solution I can see for versioning is to make a dev app and a live app, with each pointing to their respective repositories. This solution doesn’t sit right with me because I would have to go through the new application process twice for each app I want to make for Facebook.

I know that Matt Huggins wrote an article addressing the same issue, his suggestion of a sandbox would be perfect for a Dev repository. I was wondering how other developers are handling versioning.

Pretty accurate but add more swearing.