Using CVS, I have each developer keep their own source tree and commit changes to the repository on a regular basis. Then I have a "fake" user (called "test", or "prod", or whatever) that I use to check out a source tree whenever I get ready for a release. Prior to a release, I get all the developers to commit all their changes, then I check out the whole project tree using the "test" user and deploy it from there. If everything checks out OK, I have the "prod" user check out the updated code and deploy on the production server.
John H. "Nusairat, Joseph F." <[EMAIL PROTECTED]>@orionserver.com on 01/15/2002 02:00:59 PM Please respond to Orion-Interest <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] To: Orion-Interest <[EMAIL PROTECTED]> cc: Subject: RE: How to handle multiple developers I actuallly meant more in terms of storing the class files and then jaring them together. DO u all just store them on a shared drive instead?? And then alll jar em??? Joseph Faisal Nusairat, Sr. Applications Developer WorldCom tel: 614-723-4232 pager: 888-452-0399 textmsg: [EMAIL PROTECTED] -----Original Message----- From: Simon Kelly [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 15, 2002 2:55 PM To: [EMAIL PROTECTED] Subject: RE: How to handle multiple developers Use a Code Management tool such as Microsoft Visual SourceSafe or CVS(free)! Check out this link: http://www.martinfowler.com/articles/continuousIntegration.html Regards, Simon. > -----Original Message----- > From: Nusairat, Joseph F. [SMTP:[EMAIL PROTECTED]] > Sent: Tuesday, January 15, 2002 8:11 AM > To: Orion-Interest > Subject: How to handle multiple developers > > I was wondering how do u guys wrap up an application and store it when u have multiple developers coding for the same app? > > -joseph > > Joseph Faisal Nusairat, Sr. Applications Developer > WorldCom > tel: 614-723-4232 > pager: 888-452-0399 > textmsg: [EMAIL PROTECTED] >
