Best source control?

[Greg]

We are about to implement Flare and I am seeking recommendations for which source control to use.

TIA

[RamonS]

I don't think there is a "best", but there surely are some that are better than others depending on circumstances. Which source control system do the developers use? If it is one that Flare natively supports I'd piggyback on that. Makes it easier to integrate help into build and deploy processes. If you are not attached to a development department or do not get access to their systems I'd go with Git. It is the most modern free source control tool. Found instructions for it here: https://www.madcapsoftware.com/blog/201 ... e-project/

[ChoccieMuffin]

I use SVN with Tortoise as my interface, but I DON'T integrate with Flare, as I've read the horror stories on the forums about the negative effect on speed and my machine is painful enough as it is. So I do all my checkins and checkouts outside of Flare.

[Robotman]

We use SVN and have integrated it with Flare.

No major horror stories to report although we have dipped our toes in the water by including some smaller projects first. The only things I have been concerned about are wholesales changes where we have found it better to make changes progressively (example - topic changes first, then TOC). Still, if things go pear-shaped when lots of changes have been made we can always rebind (not that I want that to be a solution but it's a learning experience).

We are about to merge a number of our projects, though, and place into Source Control so we will be doing thorough testing then.

[Dee Vincent-Day]

We have GitLab and I have not had any horror stories to report. However I have learned to use git outside of Flare because sometimes I want to do something such as merging branches, which cannot be done within the GIT integration. Using Tortoise Git as the interface.