Subversion workflow - Should your production site be a working copy?

[eluser]n0xie[/eluser]
That's what the export function is for.

Why shouldn't you use a 'working copy' (i.e. revision) as your production version? Take a look at tagging.

We tag a 'stable' revision, and push that to our production servers.

Our development cycle basically looks like this: make some changes, commit. Make some more changes, commit. Then if you are satisfied, tag that revision, and push that to production. Repeat Ad infinitum.

In case something breaks, role back to a previous 'stable' revision and fix the problem. Just make sure you never overwrite config files. A good habit is to exclude the config folder as well as the index.php from SVN.