# The following was supposedly scribed by
# Ben Collins-Sussman
# on Wednesday 07 July 2004 02:12 pm:
>The book says:
>
>"The most common reason to dump and load a Subversion repository is due
>to changes in Subversion itself. As Subversion matures, there are times
>when certain changes made to the back-end database schema cause
>Subversion to be incompatible with previous versions of the repository.
>The recommended course of action when you are upgrading across one of
>those compatibility boundaries is a relatively simple process."
>
>So from this, you inferred that *every* new release of Subversion
>involved a database schema change? If so, how can we change the wording
>to make it clear that this is not the norm?
How about a section "Upgrading Subversion" before "Migrating a Repository".
In the "Upgrading" section, you can say "across minor version changes, simply
shutdown the server, upgrade, and restart".
Then have a big WARNING box advising that "major-version upgrades will most
likely require a dump and load (check the CHANGES file)" then direct the
reader to the "Migrating" section.
If the subversion developers have decided to make it a policy to only change
the database format at major version numbers from 1.0 on, that would be good.
Thanks,
Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 7 21:31:28 2004