version control - Locking files in collaboration work -
so company uses force.com , force.com ide in order develop our platform , growing company developers around world , our projects becoming bigger , bigger need way lock files nothing can overwritten. have read says locks aren't useful or use git git creates repos of files , keeps backups literally want access file , not give else access file until release it. ensure changes make saved , not overwritten accident , make collaboration whole lot easier. know thing can use in order accomplish goal? preferably not command line , integration force.com ide pretty eclipse bunch of force.com plug-ins pre-packaged.
quick answer
what asking core functionality in rcs , cvs; these revision control systems provide write-locks on files (although locks breakable) no 1 else can commit if 1 user has file checked out writing.
imho
having said that, it's cumbersome , rather horrible way collaborative development. unnecessarily serializes processes can otherwise run in parallel. example, if , collaborating, , adding new feature software in same module (using same file), whereas find bug in current version need fix in order continue work on release branch, forced lock not work.
you should @ consequences of hard enforcement of write-locked files; end creating more problems in environment in long run. coming on 20 years of experience in managing large software development projects. humbly suggest give git, svn or bzr serious , thorough study before chose archaic approaches of rcs or cvs.
Comments
Post a Comment