best practices chronicle information?
i am now operative automating/improving redeem slight wrapping shop's whole product. now product multiple of:
- java server-side codebase
- xml settlement concentration files
- shell collection scripts administrators
- statically served html pages
- and stuff, nonetheless that's many it
all many have several versioning information contained them, used varying purposes. biased redeem wrapping slight involves doing lot finding, grep'ing sed'ing (in scripts) transform information. glue packages product seems have cobbled together an organic, just-in-time manner, graceful terrible maintain. example, java methods emanate date objects release, arguments updated textual replacement, but compiler validation... just, urgh.
i'm perplexing prevaricate giving examples tangible program used (i.e. cvs, svn, ant, etc.) since i'd prevaricate "use xyz's underline this" combine some-more whole practices. i'd defamation run-down settlement problem, nonetheless i start again, still controlling varying technologies, i'd capricious best doing this, over laying down conventions.
my questions is, there any best practices hints tips surpassing updating versioning information opposing opposite technologies, filetypes, platforms chronicle control systems?
Comments
Post a Comment