Quoting Seano <[EMAIL PROTECTED]>: > Newbie subscriber here. Welcome.
> Have been wondering what techniques you guys use for ' version control'. Warning! You have opened a BIG can of worms! Mostly friendly worms, but very territorial. My suggestion, as a manager (who also codes, thankfully) in this area, is that you need to combine the best tools you can get into an end-to-end solution. Here's how I work (which is, not coincidentally, how my 8+ person team works). - all developers have standalone complete workstations (CFMX 6.1, Apache, access to shared dev DB instance); - everybody uses Eclipse with the CFEclipse plugin, althouh we can cope with users of Dreamweaver MX; - we have a Linux-based CVS server for source control. Any developer can check in/out (and MUST do so each day for complete work). There are a few around here who prefer Subversion, and it's an equally valid source control solution. Both CVS and Subversion are free and Open Source. This is a Good Thing; - it is VERY important that you have an issue/bug management solution in place. Our Help Desk users, testers, project managers and dev staff have access at appropriate levels. We used to run Bugzilla (which I happen to really like), but several of our user-level folk found it intimidating, so we have swapped to Mantis, which is a little friendlier, but still very powerful. - we have two designated Deployment Managers, who are the ONLY people authorised to produce tagged builds from CVS for Testing, QA and Deployment - we have a lengthy, multi-stage, insanely tightly documented test process, passing through integration, functional and user acceptance stages before anything gets deployed to production. - you CAN automate builds with something like ANT (which has strong hooks in Eclipse). We still build by hand on a fortnightly cycle. Week A is for test builds, Week B is for prod builds. Frankly, while this might look like overkill for a small shop, it's not. Far from it. You are better off doing this, even as a single developer, than missing out steps which might cause a problem. > On our site of 200 cfm pages, I have a constant stream of bug and > enhancement requests. Some need to go into Qa testing (separate box). Mantis, Bugzilla or another option will make a BIG difference to your ability to keep on top of this stuff. > With a Windows dreamweaver dev box and a secure Solaris product box, what's > the best way to keep control of the whole show? Get a cruddy old box that's unused in a storeroom somewhere. Install Fedora Core Linux on it. Install CVS, Apache, an issue-management app, and probably a CVS browser like CVSWeb. Go crazy! Links to help you on your way: CVS - www.cvshome.org Subversion - subversion.tigris.org Eclipse - www.eclipse.org CFEclipse - cfeclipse.tigris.org Bugzilla - www.bugzilla.org Mantis - www.mantisbt.org Steve -- Stephen Collins E [EMAIL PROTECTED] W http://www.stephencollins.org ICQ 1014940 Skype trib22 MSN [EMAIL PROTECTED] -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GIT d(---)@ s:>- a C++++$ UL++$>++++ P+>+++ L++ !E W+++$ N o? K? w !O !M !V PS+(+++) PE Y+>++ PGP++>+++ t(++)@ 5++ X+(+++) R(+++) tv b++>++++ DI++++ D+(+++)@ G+ e++ h---- r+++ y++++ ------END GEEK CODE BLOCK------ Decode geekcode at http://www.joereiss.net/geek/ungeek.html ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
