So we've been using subversion for a little while with a dev server and a production server, and things have been great. We make changes on dev, commit them into subversion, and update on production (we have the code tree checked out on both).
Now we're planning to add a staging server to the mix. So code would get developed on the dev server, committed and updated to the staging server, and then when it passes QA, committed and updated on the production server. I am not too sure how to do this, since we have the same code tree checked out on both dev and production. I don't want changes meant for the staging server to accidentally go to production, until they are ready. Is anyone using subversion in this configuration? (dev, staging, production). How do you have things set up and how do you manage deployments? Russ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:235469 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
