It has been a week since we launched Springloops in beta stage. We are very happy with input that we have received.
Currently we are applying minor bug fixes. Next major release is coming soon. There we will introduce some new cool features that will help you provide high quality code. We have much to show!
The essential element of a project in Springloops is its source repository - the place where your code is stored. The significant feature of the source repository is that it remembers each state of your project. Hence, your source is safe from lost files and overwritten changes. Creating a new project, you are asked only to provide the project name. As you can notice, below the name form, there is also generated a URL address to the source repository.
We connect with the repository every time we update files with our teammates changes or send your changes.
Conflicts do not occur very often. Yet, they arise when working with versioning systems to protect you from overwriting your teammates changes. When you edit a file, your teammates changes are merged with your changes automatically by the versioning system in Springloops. When you want to update your working copy with a change of a line which has been also changed by someone else, a conflict occurs. By conflict you are asked to choose which changes should apply - your or your teammates changes edited at the same time. You need to resolve this conflict to be able to commit your changes. You can do it manually or with your Subversion client.
There is plenty of Subversion clients available free for various systems. We have listed many of them here. If you are using any IDE try to find Subversion plug-in for it, firstly. Personaly we like SmartSVN (multiplatform), SvnX for Mac OS X and TortoiseSVN for Windows.
We are always open to your needs and ideas. If you need our direct support or have something you want to share contact us.