SVN 1.3 VS 1.5(最新) [英] SVN 1.3 VS 1.5 (latest)
问题描述
我们的IT人员已安装SVN 1.3，当前版本为1.5.
我们正在从CVS迁移到SVN，所以坚持使用1.3是否会造成很多损失?
我喜欢运行CVS2SVN并迁移到SVN，而无需编写任何脚本.
另外:在CVS中，我们的项目中有多个目录.
SVN的最佳做法是什么?
有一个夜间构建，必须从同一CVS项目中的不同目录中提取内容，才能构建夜间构建.因此，我必须牢记这一点，并且必须修改脚本以从不同的存储库中签出内容.
Our IT guy has installed SVN 1.3, the current version is 1.5.
We are migrating from CVS to SVN, so do I lose much by staying with 1.3?
I like to run CVS2SVN and move to SVN without the need of writing any scripts
Also: in CVS we have on project with multiple directories in there.
What is the best practice in SVN?
There is a nightly build that has to pull in stuff from different directory in the same CVS project in order to build the nightly build. So I have to have that in mind and I have to modify the script to check things out from different repositories.
推荐答案
最大的缺失功能是任何种类的合并跟踪.在版本1.5中添加了该功能.您可以将客户端升级到1.6，但是如果服务器是1.3，则不会启用它.
The biggest missing feature is any kind of merge tracking. That was added in version 1.5. You can upgrade your client to 1.6, but if the server is 1.3 then this is not enabled.
然后，您将获得许多性能增强. 1.3服务器可能会变慢，特别是对于大型二进制文件.您可以打包服务器文件存储库以节省1.6中的空间.
Then you have lots of performance enhancements. The 1.3 server is probably going to be slower, especially for large binary files. You can pack the server file repository to save space in 1.6.
无相对svn:externals，已在1.5中添加.有一种新的HTTP URI格式，因此无需设置任何ViewVC，您只需通过mod_dav_svn就可以看到较旧的版本.
No relative svn:externals, which was added in 1.5. There's a new HTTP URI format so without setting up any kind of ViewVC you can see older versions just via mod_dav_svn.
1.3中没有svnsync，这可能会使创建备份更加困难.
There's no svnsync in 1.3, which may make creating backups harder.
如果您还包括客户端更改，那么您将缺少部分结帐改进，加密形式的密码缓存等.
If you also include client changes, then you would be missing partial checkout improvements, password caching in encrypted form, etc.
加上1.3版以来的所有错误修复，现在已有4年之久了！
Plus all the bug fixes that have gone into the code since 1.3, which is now about 4 years old!
这篇关于SVN 1.3 VS 1.5(最新)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
