Revision control

Subversion has a few interesting ways of managing releases. The obvious one is the revision number – you committed revision 1234 to Subversion from your local workstation, then you “exported” revision 1234 to Dev, tested, signed off, and as a final step (once you’re happy with your testing) you export revision 1234 to the QA machine. (The process then repeats, but with different testers/QA people, and with UA -> Production instead of Dev -> UA)....

**Always Have a Single, Authoritative Source For Your Schema ** Everyone should know where the official schema resides, and have a frictionless experience in getting a fresh database setup. One should be able to walk up to a computer, get the latest from source control, build, and run a simple tool to setup the database (in many scenarios, the build process can even setup a database if none exists, so the process is one step shorter)....

SVN – revision control SVN – revision control email@www.shafiq.in Coordinating projects● Problem: How to coordinate and synchronize code  between multiple developers on a project? – Work on the same computer, take turns coding  Nah…  – Send files by e-mail or put them online. Lots of  manual work. – Put files on a shared disk. Files get overwritten or  deleted. Lots of direct coordination. – In short: Error prone and inefficient....