The solution we use at ATCC.org is only to work on branches. Then once things have been tested, they are merged back into the head. You resolve any conflicts on the head then retest. Once that's been approved its deployed to production.
Regards, larry -- Larry C. Lyons Web Analyst BEI Resources American Type Culture Collection http://www.beiresources.org email: llyons(at)atcc(dot)org tel: 703.365.2700.2678 -- > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of RADEMAKERS Tanguy > Sent: Thursday, February 08, 2007 10:10 AM > To: cfcdev@cfczone.org > Subject: RE: [CFCDEV] RE: DW vs Eclipse > > > maybe not *always*, but look at it this way: after you check > in that "broken" revision, it will propagate to all your > colleagues next time they update [1]. That's not going to > increase your popularity around the office. Doesn't really > matter in small teams, more in bigger teams. > > Regs, > /t > > [1] assuming the normal case where all/most devs work on HEAD > or at least the same branch. You can set up a "one branch per > dev" model, but then you spend loads of time and brain juice > merging changes from one branch to another. > > > >-----Original Message----- > >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > >Of Tom Chiverton > >Sent: Thursday, February 08, 2007 3:44 PM > >To: cfcdev@cfczone.org > >Subject: Re: [CFCDEV] RE: DW vs Eclipse > > > >On Wednesday 07 Feb 2007, RADEMAKERS Tanguy wrote: > >> before being able to see it on your dev server. Plus this > >means you will > >> have lots of non-working checkins in svn. > > > >You shouldn't get hung up on always having a working HEAD. > > > >-- > >Tom Chiverton > >Helping to adaptively seize integrated paradigms > > > >**************************************************** > > > >This email is sent for and on behalf of Halliwells LLP. > > > >Halliwells LLP is a limited liability partnership registered > >in England and Wales under registered number OC307980 whose > >registered office address is at St James's Court Brown Street > >Manchester M2 2JF. A list of members is available for > >inspection at the registered office. Any reference to a > >partner in relation to Halliwells LLP means a member of > >Halliwells LLP. Regulated by the Law Society. > > > >CONFIDENTIALITY > > > >This email is intended only for the use of the addressee named > >above and may be confidential or legally privileged. If you > >are not the addressee you must not read it and must not use > >any information contained in nor copy it nor inform any person > >other than Halliwells LLP or the addressee of its existence or > >contents. If you have received this email in error please > >delete it and notify Halliwells LLP IT Department on 0870 365 8008. > > > >For more information about Halliwells LLP visit www.halliwells.com. > > > > > > > >You are subscribed to cfcdev. To unsubscribe, please follow > >the instructions at http://www.cfczone.org/listserv.cfm > > > >CFCDev is supported by: > >Katapult Media, Inc. > >We are cool code geeks looking for fun projects to rock! > >www.katapultmedia.com > > > >An archive of the CFCDev list is available at > >www.mail-archive.com/cfcdev@cfczone.org > > > > > > > You are subscribed to cfcdev. To unsubscribe, please follow > the instructions at http://www.cfczone.org/listserv.cfm > > CFCDev is supported by: > Katapult Media, Inc. > We are cool code geeks looking for fun projects to rock! www.katapultmedia.com An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org You are subscribed to cfcdev. To unsubscribe, please follow the instructions at http://www.cfczone.org/listserv.cfm CFCDev is supported by: Katapult Media, Inc. We are cool code geeks looking for fun projects to rock! www.katapultmedia.com An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org
