Thanks guys, feel much better about it all now :) Tom, why do you keep them all in the one repository and not setup different repositories for each project?
Dan On 13/12/2007, Andrew Scott <[EMAIL PROTECTED]> wrote: > > There is no hard fast rules, but what best suits you. > > Here is what we do, and this applies mainly to more than 1 developer. If > one developer then you can ignore the fact that you don't need to merge / > sync code as much. > > 1) Create a repository with a trunk / branch / tag > 2) Write code. > 3) Sync with repository, and merge any changes. > 4) then update changes from others if it is needed. > > > The idea behind a stable repository, is that when someone else updates it > will not break anything that they need to do. This is important to try to > maintain as much as possible, not always applicable because bugs can and do > happen but with great test coverage as unit testing etc, you can minimize > this as much as possible. > > Any time you make your product live, and start to work on another version > it is best to branch the code. This is basically making a snapshot of the > current stable released version. The idea is that if you then begin on > version XX.YY then you can easily switch between versions to fix enhance > or what ever you need to do. > > This has got be the most important feature we use, the ability to switch > between a branch and trunk version at will, and have the ability merge / > sync code between them in needed. > > > > > > On 12/13/07, DannyT <[EMAIL PROTECTED]> wrote: > > > > I've seen a couple of threads on this but not enough for a definitive > > conclusion. > > > > I'm trying to define a standard practice for source controlling a flex > > and back-end project (namely flex -> remoting -> .net ( -> sql?) > > > > Do people tend to treat their server-side projects as a separate project > > in a separate repository? > > > > With everything in the one repository you can keep local compilation > > consistent and check-in build scripts, however by splitting up into multiple > > projects you're keeping flexibilty and managability by not bloating your > > repository. > > > > I guess it'll come down to preference but was just wondering what others > > are doing, as a general rule our developers currently will be dealing with > > both client side and server side projects but down the line i'd like to see > > clearer separation of roles. > > > > Any thoughts or practices people can throw in would be much appreciated. > > > > Dan > > > > -- > > http://danny-t.co.uk > > > > > > -- > > > > Senior Coldfusion Developer > Aegeon Pty. Ltd. > www.aegeon.com.au > Phone: +613 8676 4223 > Mobile: 0404 998 273 > > > -- http://danny-t.co.uk
