|
|
Project management
Date: 01/14/07
(Web Development) Keywords: software, database
Looking for anyone's experience in coming up with some sort of deployment system to bring together 4 different programmers on a project that needs to be built rapidly.
I am pretty well versed in subversion, but the way the lead of my new company is explaining, the individual developers will need to be able to modify the site's core library at will. And the concern with this is, what if one developer breaks a needed component...suddenly the other 3 programmers are at a work stoppage until it's fixed. So he suggested creating 4 branches of the main repository for the other dev's and me. This way each Dev has their own code base to modify at will. This seems a little crazy, but maybe I am missing something here.
From my understanding, you can remerge different branches together...but to do so requires manually walking through diff's of conflicting revisioned files. So unless we merge all 4 branches on a weekly basis, this will be one massive cluster -ck eventually at the end.
Some quick thoughts on my own:
Dedicating one of the 3 programmers to developing the core library, basically giving him/her a "I need this functionality" memo or something.
Coming up with some sort of per-file branching scheme when a dev has to edit a library/base system.
Any comments or suggestions would be greatly appreciated.
Update
To clarify my problem, we have a version/source backup/management software system(subversion) decided upon, it's just a question of how to use it correctly to meet our needs.
Programmer a,b,c might all be working on separate branches of the application, but suddenly programmer A breaks a database abstraction class in the core of the whole thing, the end of the day comes and A commits the work in progress. The next morning B,C update their working copies, grabbing the broken DB class and bam workstoppage
Source: http://community.livejournal.com/webdev/382972.html
|