Chris, Thanks for your comments. I am looking forward to using SVN. So far my experience with SVN has been great. I always use the SVN update before i begin a new set of changes. It has worked flawlessly for me so far.
Mike On Fri, Jan 8, 2010 at 9:38 AM, Chris Champion <[email protected]>wrote: > Mike-- > > I'm using a subversion repository in that respect, as an integral part of > the promotion of code to dev/qa/production, very much like you're > considering. One difference is that we do have a separate server for SVN > instead of putting it on the dev server. > > Each major project gets its own repository, with dev/qa/prod branches in > it. I don't know if that's the best way to do it, but it does pretty well > for us. > project1/dev/file1.cfm > project1/qa/file1.cfm > project1/prod/file1.cfm > > Basic workflow: edit on workstation, check into SVN, export from SVN to > dev. > If all goes well, merge changes from dev to qa branch in SVN, export to QA. > Lather, rinse, repeat for production. > > If we're in the middle of a bunch of work on dev and someone finds an > urgent bug on production, someone synchs their workstation to the QA or prod > branch, fixes it & tests on QA, and checks it into production. > > Take a look at the "svn export" command, it is very handy for what you > need-- exports code but omits all the hidden files & directories that svn > uses for tracking. svn status and svn diff will also become your friends. > > -CPC > > > On Fri, Jan 8, 2010 at 8:12 AM, Mike Demahy <[email protected]>wrote: > >> I have started using subversion. Thanks to Ken Auenson. I have been >> working with him on a project and we are using Subversion to manage the >> code. I can definitely see the benefits of using it. >> >> I want to set-it-up with my existing projects. And I would like some >> advice on the best practice. >> >> I have several projects that I maintain. I want to setup each project >> with its own repository. I want to be able to promote my changes to >> production with subversion. >> >> I currently develop on my laptop then upload to development and finally >> production when ready to release my changes. >> >> I am thinking of setting up the repository on the development server. I >> can update the code one my laptop, commit those changes to the Development >> server when I am ready to test them. Then when I am ready to release the >> changes to production, I can promote the changes to production from the >> repository. >> >> Finally my question, is this the best way to set up the Repository? >> >> I would appreciate any suggestions >> >> Thanks, >> >> Mike Demahy >> >> > -- > You received this message because you are subscribed to the "Houston > ColdFusion Users' Group" discussion list. > To unsubscribe, send email to [email protected] > For more options, visit http://groups.google.com/group/houcfug?hl=en >
-- You received this message because you are subscribed to the "Houston ColdFusion Users' Group" discussion list. To unsubscribe, send email to [email protected] For more options, visit http://groups.google.com/group/houcfug?hl=en
