svn checkout trade prolongation environment?


in digest i am operative on, have an ongoing contention among dev organisation - should prolongation sourroundings deployed checkout svn repository an export?



the growth sourroundings apparently checkout, given constantly updated.
for production, i'm personally checking out sure trunk, given creates destiny updates easier (just run svn update). however devs opposing it, svn creates files group/owner permissions svn slight (this linux os, those things matter), also carrying .svn directories prolongation seem rather dirty.



also, checkout - pull sole comforts prolongation but including in-development code? tags bend out any feature? any alternatives?



edit: i competence have pristine - requirement means constantly means pull fixes prolongation environment. wish prevaricate finish build (which takes many longer rudimentary update) only pulling vicious fixes.



Comments

Popular posts from this blog

list macos calm editors formula editors

how hibernate @any-related annotations?

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?