Apache Subversion vs. GitKraken

Subversion solves our software versioning problem by providing tools for conflict resolution when doing collaborative work on the same files and projects. We use it with TortoiseSVN and it works great for some of our projects with smaller teams. However, we have a need to make code reviews more and it is a little more difficult to do that in SVN, compared to Bitbucket and Git.

Incentivized

Axosoft is well suited as a project management tool for software teams looking to track workloads. Great tool for categorizing features, tasks, bugs, or a customized category into sprints. Companies can take advantage of the tracking aspects to create burndown charts or just to track employee time. I would say it is less appropriate for small task management like a to-do list type application because it has so many features that would go to waste. Furthermore, Axosoft is more geared towards development teams, but you could use it across departments if needed.

Incentivized

• Track and control concurrent versions of the same files.
• Has good support from many different software, including visualization, DevOps toolchain.
• Well documented and understood by developers as it has been around for a long time.

Incentivized

• Creating pull request
• Connection to various services
• Git flow

Incentivized

• Refactoring the layout of a respoitory--or a part of a repository--can be a bit painful, especially for users with workspaces associated with the affected part of the repository. Not sure what could be done to make that better, but it would be nice if something was possible.
• Folks coming from Git can have problems using Subversion. Again, not sure anything can (or should) be done to address that, but it is occasionally an issue.

Incentivized

• A bit hard to use, or a steep learning curve. The UI isn't super intuitive at first, it took me awhile to pick it up and I had to get someone to basically show me what they recommend I set my filters and UI to.
• This might be a case of improper setup but when making tickets, there isn't an auto response, so we get a lot of duplicate tickets if a conversation happens on the emails before someone takes the case and replies through OnTime.

Incentivized

While there are interesting alternatives, such a GIT, Subversion has been a breath of fresh air compared to its predecessors like CVS or Microsoft Source Safe (now called Team Foundation Server). Its ease of use and high adoption rate is going to keep me using this product for years to come.

Once you get the hang of Axosoft, I think it's easy to use however... getting the hang of it takes quite a bit of time. Additionally, once Axosoft makes an update, it can be difficult to find your bearings again. Like I said, once you know how to use the product, I think it's easy but it takes a bit to become comfortable and confident with Axosoft

Incentivized

After Microsoft Visual SourceSafe was discontinued, we chose Subversion and it was a great choice. We were able to migrate to Apache Subversion very quickly and easily and benefited immediately from its non-locking workflow (SourceSafe required users to "lock" the file when editing to prevent editing conflicts from other users, whereas Subversion allows multiple users to edit the same file simultaneously and then merge conflicts later.)

While we still use Apache Subversion for our legacy projects, we've migrated to Git and GitHub for our new projects as that is the new "cool kid" and it provides some benefits such as distributed and offline development. But Git is more complex than Apache Subversion and not as easy to learn.

Incentivized

Updated technology and ease of use make GitKraken stand out against other products we've used in the past.

Incentivized

• It allowed us to deliver the right files to our customer without "clobbering" previous releases, making for a far more satisfied customer.
• It allowed our developers to work on two releases in parallel (plus an occasional third, for emergency fixes).
• With some simple hooks, it allowed us to set up a system where code was was automatically deployed to test servers as soon as developers committed it, making testing easier. This was made easier by virtue of being a ColdFusion project, which requires no compilation. However, that is possible for compiled code with a continuous integration system like Jenkins.

Incentivized

• Axosoft has positively affected the time management of our employee resources
• Axosoft has shown us where we have inefficiencies in the organization
• Axosoft has allowed us to track projects better, get them out on time allowing for more projects to be scheduled and, in turn, increased our subscriber count.

Incentivized