Старую - сейчас у меня клиент сборки 2005 года, до того был ещё старее. Цитирую: Perforce - corporate standard. I'm not an expert, but would ask - why so many praises? It has: - only one sandbox ("depot") per a PC; - it's GUI client (v 2005.2) is unable to diff versions in-place, you have to type revision numbers; - it's merge tool GUI is overloaded; - it's security system is inevident; - it's unable to show a changelist's changes to command line; Yes it's integrated with bug tracker, but if it's a bad SCS, I wuoldn't use it.
I used SVN for some time, and besides some slowness because of its versioning system and inevident branching, it suited us pretty well.
In MS Visual Studio before v2005, SCS support is buggy itself, so no SCS integrates smoothly with it.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
8/2/07 08:13 (UTC)Цитирую:
Perforce - corporate standard. I'm not an expert, but would ask - why so many praises? It has:
- only one sandbox ("depot") per a PC;
- it's GUI client (v 2005.2) is unable to diff versions in-place, you have to type revision numbers;
- it's merge tool GUI is overloaded;
- it's security system is inevident;
- it's unable to show a changelist's changes to command line;
Yes it's integrated with bug tracker, but if it's a bad SCS, I wuoldn't use it.
I used SVN for some time, and besides some slowness because of its versioning system and inevident branching, it suited us pretty well.
In MS Visual Studio before v2005, SCS support is buggy itself, so no SCS integrates smoothly with it.