Re: How do you TEAM Code?

This WebDNA talk-list message is from

2004


It keeps the original formatting.
numero = 58121
interpreted = N
texte = Yes, I mean many developers working with the "same" code. So if I understand you right, we create a branch for each developer. He/She works within that branch and then when we want to release a version we merg= e the changes with the "head"? I think the multiple test sites for development are not needed since the developers have their own copies locally, but I am not sure if this is the "correct/comon" way of doing this. Nitai On 28.5.2004 17:29 Uhr, "John Peacock" wrote: > Nitai @ ComputerOil wrote: >=20 >> Yes, but that does NOT solve the locking of files (so that not you and >> someone else can work on the same time on the same file) and versioning = of >> your code. >=20 > Databases should not be versioned resources, typically. If you have > multiple developers making multiple changes to database headers, you > only choice is branches and multiple test sites for development. If you > use exclusively relative path names for all files, you can do this >=20 > http://developer1.test/site1 > http://developer1.test/site2 > http://developer1.test/site3 > http://developer2.test/site1 > http://developer2.test/site2 > http://developer2.test/site3 > ... etc. >=20 > and then each developer gets his/her own branch both at the CVS level > and at the web server level. >=20 > BTW, "Team Programming" is usually described as more than one person > developing the same files at the same time (often with the same monitor > and keyboard for Extreme Team Programming). I think you are just > talking about multiple developers interacting with the same sites, so > that is why I gave the advice above. >=20 > You might also want to check out Subversion: >=20 > http://subversion.tigris.org >=20 > which is to a large extent the CVS - The Next Generation... >=20 > John --=20 Tools to energize your business Web Content Management =ABRedakto=BB & eBusiness Systems ComputerOil=AE AG Dammstrasse 7 5400 Baden / Switzerland Telefon +41 (0)844 44 55 66 info@computeroil.com http://computeroil.com ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: How do you TEAM Code? ( John Peacock 2004)
  2. Re: How do you TEAM Code? ( "Nitai @ ComputerOil" 2004)
  3. Re: How do you TEAM Code? ( John Peacock 2004)
  4. Re: How do you TEAM Code? ( "Phillip Bonesteele" 2004)
  5. Re: How do you TEAM Code? ( "Dan Strong" 2004)
  6. Re: How do you TEAM Code? ( John Peacock 2004)
  7. Re: How do you TEAM Code? ( "Dan Strong" 2004)
  8. Re: How do you TEAM Code? ( Donovan Brooke 2004)
  9. Re: How do you TEAM Code? ( "Dan Strong" 2004)
  10. Re: How do you TEAM Code? ( John Peacock 2004)
  11. Re: How do you TEAM Code? ( Donovan Brooke 2004)
  12. Re: How do you TEAM Code? ( "Nitai @ ComputerOil" 2004)
  13. Re: How do you TEAM Code? ( John Peacock 2004)
  14. Re: How do you TEAM Code? ( "Nitai @ ComputerOil" 2004)
  15. Re: How do you TEAM Code? ( "Dan Strong" 2004)
  16. Re: How do you TEAM Code? ( "Nitai @ ComputerOil" 2004)
  17. Re: How do you TEAM Code? ( Dylan Wood 2004)
  18. How do you TEAM Code? ( "Nitai @ ComputerOil" 2004)
Yes, I mean many developers working with the "same" code. So if I understand you right, we create a branch for each developer. He/She works within that branch and then when we want to release a version we merg= e the changes with the "head"? I think the multiple test sites for development are not needed since the developers have their own copies locally, but I am not sure if this is the "correct/comon" way of doing this. Nitai On 28.5.2004 17:29 Uhr, "John Peacock" wrote: > Nitai @ ComputerOil wrote: >=20 >> Yes, but that does NOT solve the locking of files (so that not you and >> someone else can work on the same time on the same file) and versioning = of >> your code. >=20 > Databases should not be versioned resources, typically. If you have > multiple developers making multiple changes to database headers, you > only choice is branches and multiple test sites for development. If you > use exclusively relative path names for all files, you can do this >=20 > http://developer1.test/site1 > http://developer1.test/site2 > http://developer1.test/site3 > http://developer2.test/site1 > http://developer2.test/site2 > http://developer2.test/site3 > ... etc. >=20 > and then each developer gets his/her own branch both at the CVS level > and at the web server level. >=20 > BTW, "Team Programming" is usually described as more than one person > developing the same files at the same time (often with the same monitor > and keyboard for Extreme Team Programming). I think you are just > talking about multiple developers interacting with the same sites, so > that is why I gave the advice above. >=20 > You might also want to check out Subversion: >=20 > http://subversion.tigris.org >=20 > which is to a large extent the CVS - The Next Generation... >=20 > John --=20 Tools to energize your business Web Content Management =ABRedakto=BB & eBusiness Systems ComputerOil=AE AG Dammstrasse 7 5400 Baden / Switzerland Telefon +41 (0)844 44 55 66 info@computeroil.com http://computeroil.com ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ "Nitai @ ComputerOil"

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

SiteCheck & WebCat ? (1997) Not really WebCat- (1997) PCS Frames (1997) dynamic list of form variables (2003) Reminder for beta testers (2000) Using Plug-In while running 1.6.1 (1997) Upload Maximum (2003) include bug????? (1997) [WebDNA] mod_WebDNA_apache2.2.so: mach-0, but wrong architecture (2010) Duplicate Cart ID (2001) my price won't move (1997) Problems appending to database (1997) Press Release hit the NewsWire!!! (1997) WebCat2 as a chat server? (1997) Upgrading old WebCat Database Files (1997) WC2b15 - [HTMLx]...[/HTMLx] problems (1997) Date search - yes or no (1997) AAgghh!! Help, please. SSL strikes again. (1997) [WebDNA] two ideas for running a cluster of WebDNA servers (2019) [WebDNA] Webserver does not respond occasionally (2018)