Hi, I've been using Collaborate with Beta17 without any problems. I'm about to upgrade to Beta19, but just wanted to say that after trying out Git, Mercurial, and PlasticSCM (which all have their advantages/disadvantages), it's nice to have a form of version control integrated in the editor, so thanks! I noticed on the Unity blog post a while ago that after some testing and feedback, branching would not be included. I was thinking about things like how branching can help with release versions, and trying to issue patches and fixes for those releases while working on new features. It would seem very helpful to also be able to bring those fixes in to a branch where new features are being worked on. With Collaborate, how do you envision being able to handle similar scenarios? I guess we could create a new repository for newer versions/features, but then we wouldn't be able to bring in the fixes on the release repository. I noticed there were other comments on the blog with concerns about this as well. Also, many times I find that I've been making changes to a particular script and then realize I want to view that same script in an older state to see what I had deleted. Unless I'm mistaken, with Collaborate it seems like I'd have to first commit all current changes, then restore an older commit to get the whole project as it was in that older state, then open the file to view the content at that time. In Git, with Sourcetree or GitKraken, you can easily see a file's history without having to checkout the whole project from a previous commit. Would you consider adding some sort of functionality like this? Thanks for your time.