(Semi-)scheduled downtime for svn.collab.net.

["C. Michael Pilato" <cm...@collab.net>]

Sometime after the 0.34 release (probably early next week), I'll be
upgrading svn.collab.net to the new code.  Which means doing
repository dumps and loads.  Which means lots of downtime (there are
quite a few repositories on that box).  In addition, I want to switch
over to Berkeley DB 4.2.50.

And since I'm going through all that pain already, I want to also
install a much newer version of the OS there, too.  That box is
running something awfully old (RedHat 6?) with a hodge-podge of RPMs
and source-built stuff (including some five versions of Berkeley DB).
It's just time for a little housekeeping.  

So here's your warning.

Now, it is *possible* that I'll be able to secure an alternative
machine on which I can install the new OS, new Berkeley DB, and new
Subversion.  That would allow the downtime to be limited just to the
time taken to perform loads of incremental dumps made from commits
which occur during the upgrade window.  But I'm warning folks of
potentially day-long downtime just in case that plan falls through.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org