The word "assume" is being a little bit overused here. =)
The development environment from company to company can be drastically different. Standard practices versus ideal practices can be discussed in more depth that is necessary. Let's take the example of Development versus Staging. if your organization offers you the ability to develop on your local machine until code freeze then your staging machine will be a non-production machine that will be ready for QA to perform intial User Acceptance Testing. So in that case would have an SVN for Development or Staging? Now throw in that testing is in freeze and is waiting to be psoted to production. Would your same SVN instance be used for Production? In my case, you have two different SVN instances or two different source control points. You could sometimes have a production push person. Now this is a scenario from a large IT budget. Would I want to keep a local SVN of my work? Absolutely! Hell, my own chagnes need to backed out sometimes. It has to deal how large your organization is, your project work flow and established standard operating procedures. SVN and CVS integration for Eclipse are often used and ahve treated many safely and with confidence their code changes are present. I moved away from DW as the caching of "sites" was time consuming when synchronizing. I also keep multiple versions of Eclipse on my systems for the type of work my clients ask for. As frustrating as it will sound, "it depends." Teddy On 2/7/07, RADEMAKERS Tanguy <[EMAIL PROTECTED]> wrote:
I'm not being picky about "dev" vs. "test". My point was about the use of svn to "... update the working copy on your dev server each time you check in some code." You shouldn't have to check in code to see your changes, you should just be able to save your file and then reload your browser (whilst java developers around you gasp in amazement). Once it's all working (well, once there are no more really obvious bugs), THEN you check it in... Or am i still misunderstanding? /t >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf >Of Sammy Larbi >Sent: Wednesday, February 07, 2007 8:56 PM >To: [email protected] >Subject: Re: [CFCDEV] RE: DW vs Eclipse > >RADEMAKERS Tanguy wrote, On 2/7/2007 1:05 PM: >> I would have assumed that you use your dev server to test your >> code...no? >> >> > >I just also assumed i "knew what was meant" and didn't focus >too much on >the exact terminology, but rather the intent of the statement. > Again, I >may very well be assuming too much, since that's two >assumptions on the >same sentence =) > > >>> -----Original Message----- >>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf >>> Of Sammy Larbi >>> Sent: Wednesday, February 07, 2007 8:05 PM >>> To: [email protected] >>> Subject: Re: [CFCDEV] RE: DW vs Eclipse >>> >>> RADEMAKERS Tanguy wrote, On 2/7/2007 12:41 PM: >>> >>>> the downside to this approach is that you have to check in a change >>>> before being able to see it on your dev server. Plus this >>>> >>> means you will >>> >>>> have lots of non-working checkins in svn. >>>> >>>> /t >>>> >>>> >>>> >>> I would have assumed that you'd be testing before checking in >>> the code. >>> But, I may have been assuming wrong. 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/[email protected]
-- Teddy R. Payne G-Talk: [EMAIL PROTECTED] Adobe Certified ColdFusion MX 7 Developer Atlanta ColdFusion User Group (ACFUG) Atlanta Flash & Flex User Group (AFFUG) 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/[email protected]
