I’m going to upgrade my company’s subversion server from version 1.6 to 1.7. The server runs on linux (Ubuntu AFAIK).
I’ve read all those:
I’ve also read those posts:
subversion-client-version-confusion
how-to-upgrade-svn-server-from-1-6-to-1-7
Here and now, I know how to perform this. It’s not a big deal. What concerns me the most is the current hooks infrastructure. There are several scripts in bash and perl.
As for now I’ve found no information referring hooks infrastructure changes, but maybe there are some known issues I missed? Is there anything against the upgrade I should know?
PS: Try and see what comes method is absolutely unavailable. I’d like the upgrade to be as fluent as possible. Repository users shouldn’t even notice any changes. I can’t allow myself any failure in that matter.
The Subversion compatibility guarantees promise that your hook scripts are called exactly the same in 1.6 as in 1.7. In 1.7 (and future versions) more arguments can be passed to scripts, but the old arguments still match the old behavior. So if you created your scripts like the templates, to ignore ‘extra’ arguments you shouldn’t see a difference.
Subversion 1.7 didn’t change the repository format since 1.6, so you can even (accidentally) use the svnlook from 1.6 to access the repository after upgrading.