drunkahol
New Member
This is the second time I've been asked to investigate the use of Subversion as a source code control tool instead of Roundtable.
Roundtable has been quite happily deployed at my previous client and runs pretty happily here too. The number of development seats is growing however, and the management want all development (Java, Perl, PHP, Ant etc etc) done under the same versioning tool.
We know that Subversion and Roundtable work in completely different ways, so there will be some re-training of the Progress developers required.
Is anyone else out there using Subversion at all? Any hints? Any things to avoid?
If not, I think we're bashing ahead with it anyway, so I'll post a reply once we've managed to complete the migration.
Cheers
Duncan
Roundtable has been quite happily deployed at my previous client and runs pretty happily here too. The number of development seats is growing however, and the management want all development (Java, Perl, PHP, Ant etc etc) done under the same versioning tool.
We know that Subversion and Roundtable work in completely different ways, so there will be some re-training of the Progress developers required.
Is anyone else out there using Subversion at all? Any hints? Any things to avoid?
If not, I think we're bashing ahead with it anyway, so I'll post a reply once we've managed to complete the migration.
Cheers
Duncan