The best way to revision a shard

[Varchild]

Yesterday I was thinking about this:
what's the best way to set up a revision on a production shard?

Upload new script files and take a backup of older?
Rename older to their revision?
Merge all in one file and use #define Rev<number> ?

I think a good way could be take progressive backups with file extension built on last file revision like RaceDefinitions.123 .

^_^

[CEO]

The best way is to use a revision control system, the way RunUO is distributed. Check out TortoiseSVN.

about: TortoiseSVN is a really easy to use Revision control / version control / source control software for Windows. It is based on Subversion. TortoiseSVN provides a nice and easy user interface for Subversion.
It is developed under the GPL. Which means it is completely free, including the source code. But just in case you don't know the GPL too well: you can use TortoiseSVN to develop commercial applications or just use it in your company without any restrictions.
Since it's not an integration for a specific IDE like Visual Studio, Eclipse or others, you can use it with whatever development tools you like.

As a Subversion client, TortoiseSVN has all the features of Subversion itself, including:

* Most current CVS features.
* Directories, renames, and file meta-data are versioned.
* Commits are truly atomic.
* Branching and tagging are cheap (constant time) operations.
* Efficient handling of binary files.

[Zippy]

Originally Posted by CEO

The best way is to use a revision control system, the way RunUO is distributed. Check out TortoiseSVN.

This is also what we use for all of the UOGamers production shards. Each has its own SVN.

Coincidentally, thats why the RunUO public svn has lots of revisions where no files (that anonymous users can see) have been changed.