2009/1/19 Nathan Rixham <nrixham@xxxxxxxxx> > > well the idea of svn is that should you find a problem you either rollback > the file(s) to the good version (not rollback the whole site) or you commit > updated files with the fix, then redeploy. No need to branch or such like. > Well, yes, of course there also will be bugs in "good" versions but I think it should more be like: "Well, there is a bug.. maybe switch 2 or 3 revisions back and than we see" and not like "Oh, a bug. maybe 100 - 150 revisions back, which were all created yesterday" By locally created and tested scripts you will of course not have those probs because you're not comitting everything. But locally developing brings some kind of care-taking like making sure you use everywhere the same version (php, mysql, webserver), installed the same extensions, have the same php.ini, than there the whole database... and php is not my main work ;) I thought with using maybe another branch all those 100-150 revisions are stored away and the main branch is than again more like, well going back 1-2 revisions is equal to 1-2 days of work. > maybe more importantly.. you shouldn't really be getting to production live > with these errors (you always will at some point) - perhaps you want to look > at unit testing, and even continuous integration/building while you're > there. all those talking was only about the developing server. Unit testing I heard of but not really understand how to use and what excatly unit testing does. ps: pdt-eclipse is great, you can integrate it right in with svn for handy > diff's, commits, updates etc (and svn in with bugzilla, mylyn loads more..) yes, I'm already using pdt-eclipse with subclipse. What's mylyn about? (again heard of ;) ) And btw: what is "scp"? -eddy
