> Please visit that link again, I've documented the r11082 change a bit more. > Basically you just need to explicitly enable the new optional component > (tracopt.versioncontrol.svn.* = enable, in the [components] section of you > <env>/conf/trac.ini file). Sorry for the disruption, we'll emphasize this > point in the upgrade notes.
IMHO, the "upgrade" command should automatically update the [components] section to transparently enable back SVN when SVN was already used for the upgraded environment. There are already far too many ways to fail a Trac installation, maybe this one could be avoided. It took me about one work day to replicate a Trac environment from our server to a local development machine. I'm not a Trac expert, but I used to know Trac and I bumped into half a dozen issues when performing this replication (most of them are due to Trac dependencies). Upgrade should be as seamless as possible, I believe. Upgrading is always a risky task, reducing the risk to stop the service for hours would be great. Just my two cents - I know it is far easier to give advice than to work on the implementation ;-) Cheers, Manu -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
