Hi,
I have noticed there is a lot of information about using SVN and Sub version for team programming, what is wrong with using the native team support built into servoy 4 ???, I am new to team programming and would like the simplest method of sharing my solution between 2-3 programmers ?, any advice would be greatly appreciated.
Thanks
Hi Philip,
The big difference between SVN (or any other flavor) and Servoy Teamserver is that the Servoy Teamserver doesn’t create new release for each commit you do to the teamserver (unlike SVN, etc.). You always commit to the same release unless you create a new releae (via the servoy-admin pages) yourself. So it’s impossible to rollback to a previous commit when you didn’t created a new release first.
Of course there are other things that Servoy teamserver doesn’t do like branching etc. but those are more power features.
So if you don’t mind to make your own releases or don’t mind that you can’t always rollback to a previous commit then Servoy Teamserver is the easiest method to work in a team.
If you do mind all these things then SVN (or the other flavors) is your choice.
Hope this helps.
Hi Robert,
Thanks for the explaination, so if I was to use the servoy team server, would it be good practice to create a new release before I commit changes, or before any of the programmers commit changes ??, so if there was a problem we could always roll back to the previous release.
Thanks
Hi Phillip,
I am not sure if there is a best practice on this yet.
If you want that safety net with Servoy’s teamserver then you should create a new release before any developer commits of course this requires some communication between the developers then as well. Or else you end up with developers creating a release while another is in the process of committing.
You don’t have these issues with SVN.