Arguments against zip files as source control
version-control
Solution
The best argument is surely that using a version control system like Subversion or Mercurial is much, much easier and more secure than messing about with zip files. I doubt there has been much paper writing on the subject, as the use of zip files for this purpose is fairly obviously wrong.
There are a number of SO questions on the general advantages of version control. For example How can I convince my department to implement a version control system? and https://stackoverflow.com/questions/250984/do-i-really-need-version-control
Problem
What arguments can be used against using zip files of source code as a form of version control? In general each developer is working on their own program and has a responsibility for it. But there are times of course when other developers are involved in work on that program. Each developer has their own naming convention for zip files ranging from appending the date, a number after the program name or even appending _old / _oldold _newversion etc… When there is collaboration on development of some code. It has to be checked who has the ‘latest’ version of the code – and where it resides, usually the correct version is identified. There is no easy existing method to diff source trees and during development unwanted changes occasionally slip into code. The zip file corresponding to software releases that have release to manufacturing are archived. This at least adds some traceability. Also before RTM there the code is peer reviewed against the previously released version so quality assurance does exist. Are there any formal white papers explaining the advantages of source control, making clear that the above isn’t a fully valid form of source control? Arguments exist here that since the end product (manufacturing releases) are under control and these are reviewed that there is no problem with the process. Developers do not have too much of a problem working with zip files in this way, but may not be aware of the advantages.