On 9/8/06, Santhosh Raghunath <sraghunath@adteractive.com> wrote:
>
> We are planning for an upgrade to Subversion 1.3.2.
>
> After downloading the tarball, noticed that the INSTALL doc has steps for
> complete installation alone. I would like to know the overview of steps
> required to do an update from ver 1.2.1 to 1.3.2.
>
> Will this involve any downtime? Are there any precautions to be taken
> before the upgrade apart from backing up the repository?
You should disable access to the repository while doing the upgrade so
there's no chance you'll get crossed up with someone doing a commit
while you're replacing binaries.
As I understand it, there's no upgrade "process", you just install the
new version the same as a "complete" installation. If you serve via
HTTP, you'll probably want to restart Apache so the new modules are
loaded.
There may be some changes to the repository format which would give
you a boost over the previous version. To take advantage, you'd
svnadmin dump the old repository, upgrade, then load the dumpfile back
in using the new version. However, you do not need to do this, as
newer versions are backwards-compatible.
The release of 1.4 is very close, you may want to consider holding off
on the upgrade until that happens so you aren't "upgrading" to a
release that's already one behind.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Sep 9 02:41:34 2006