Hi, We are using PRC, which is U2 aware. I understand your concerns but PRC does seem to address your concerns. You can have multiple programmers working on the same project and the same code, or you can provide each with a copy of the code but they'll have to merge their changes before moving the project(s) on.
The beauty of PRC is you can track what changes are made, why, and reverse the changes if needed. You also have control over what is going out to customers. Tom RATEX Business Solutions -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Anthony Youngman Sent: Wednesday, June 02, 2010 4:59 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] SB+ PA Compare I'm not a mercurial user - I'm learning git, but what's wrong with a DVCS? Yes it would be nice if each dev could have their own account, but you're assuming "one dev per DVCS instance". Why not one account per DVCS instance? But by not giving each dev their own account, you're throwing all the advantages of ANY version control system! Whether it's Mercurial, git, SCCS, CVS, Visual Source Safe, as soon as you have devs fighting over access to the source you're giving yourself a headache. Centralised system, distributed system, it's all the same. Let me give you an example method of working with git, several devs, one test environment. Pretty safe bet you can translate this into Mercurial terms easy enough. Each dev has their own test account, probably can't do an awful lot there, but they do all their coding, compiling, and basic unit testing in their own account. They can then push their changes to a branch in the central test account to test them. When they're happy, they can merge them into the main branch. If several devs are fighting over the central test account, the fact that git allows very rapid changes between branches means that one can have it for however long it takes, then revert his changes leaving it clean for the next one, so you can switch the test account rapidly. And more importantly, dev A *can't* step all over My experience of cvs's commercially was either none (for UV, had to track everything manually), or VSS for VB where it was a right pain when I had something checked out for dev work and somebody else needed it for a quick bugfix, or vice versa. Thing is, you can put procedures in place so that a DVCS has strict central control. You can't set up a centralised VCS to give several developers flexibility to work on the same code at the same time. Cheers, Wol _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
