??? 08/06/10 14:22 Read: times |
#177779 - that's no difference Responding to: ???'s previous message |
Oliver Sedlacek said:
With proper revision control you should follow the maxim of 'commit often', and I certainly commit for every bug fix or feature implemented. You can do the very same with zip/copy. Oliver Sedlacek said:
That can be several times per day. Certainly so with zip/copy. Oliver Sedlacek said:
With appropriate log messages you get a fantastic trace and you can roll back to any point. You also tag important revisions like releases, betas etc. A simple textfile does the same. You can also rename the zipfile. Oliver Sedlacek said:
The diff utility is brilliant, and can also do M$ Word files. There are bucketful of diff utilities, independent of version control. Oliver Sedlacek said: Who cares nowadays?
By storing all versions in an optimum format you save disk space compared with zipped copies. Oliver Sedlacek said: What would prevent you to do the same with zip/copy?
I also use command line utilities to embed a revision into my source so I can check what source versions went into a build automatically. Oliver Sedlacek said: Who said "manual processes"?
Subversion is free to use, and saves time and stress. It makes manual processes seem incredibly slow, error prone and inefficient. --- Oliver Sedlacek said:
I've had to organise and enhance the verification files for a product to the satisfaction of a certification body (no cheating allowed). My starting point was a bunch of paper files that are the released versions with real, old school signiatures. The working files are obviously electronic files and dumped in the design history folder. The problem was finding which files corresponded to the released versions and who had done what to them (and why). There were about 6000 files in the folder, going back over 10 years. This is no argument for or against anything. If the requirement for version control would come up at the beginning of the development, surely it would be implemented. Any requirement imposed ex post means trouble. I've come across a lot of ridiculous requirements for various certifications. Just an example, once I was told I should rewrite my sources from asm to C as the employees of the certification agency don't understand asm. It was after 10+ years of development and successful deployment etc. of the product in asm. Jan |