[ date ] 2004/02/22 | Sunday | 09:17 PM [ author ] Tels <[EMAIL PROTECTED]>
> One thing: How do we make sure that my changes don't clobber something > somebody else already worked on the time I work on it? Good communication is the key. If svn is anything like cvs on this matter, there's no locking of files like some other version control systems. Everyone who has write access to the repository is 'trusted' to do sensible things. With that said, if you're going to start making big changes on a certain section, let people on the mailing list know. This way, no one is caught by surprise when (for example) the API to a module changes or whatever. As you can imagine, letting people know about big changes is a good idea regardless of whether you're using a version control system or not. However, you don't have to chronicle your every little move. For example, if you need to reformat a few lines of code here and there or add a few comments, just do it. Use your judgement to determine what's noteworthy and what's not.
