Recently I've read this article: http://www.smashingmagazine.com/2009/09/25/svn-strikes-back-a-serious-vulnerability-found/
Developers of many popular sites like apache.org, php.net (http://ru2.php.net/.svn/entries), classmates.com and russian Yandex use SVN, but do not follow the recommendations given by SVN (to use command export
).
So, what are the reasons for not using svn export
instead of updating the public copy like all they do?
Apache Subversion which is often abbreviated as SVN, is a software versioning and revision control system distributed under an open source license. Subversion was created by CollabNet Inc.
Subversion is still used by some projects, but git has replaced it for most new projects. Many subversion projects have also migrated to git. But since subversion is open source it won't ever completely disappear.
Subversion is used for maintaining current and historical versions of projects. Subversion is an open source centralized version control system. It's licensed under Apache. It's also referred to as a software version and revisioning control system.
Introduction: Subversion (SVN) is a centralized SCM (Software Configuration Management) implementation. It allows to track changes and concurrent development on the same files. Subversion is centralized version Control system, meaning that it uses central server to store all files and enables team collaboration.
Some people, not including myself, think that to deploy onto production you should just issue an svn up. If you do an export it loses the meta data about the versioning so you can t do that, you have to use another mechanism for tracking which version is where. It is an easy solution, but I think it can make for lazy packaging and also for "fixing in production" as if you do this you can also check back in from production...
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With