Apache Subversion vs. GitKraken vs. GoProof

It's a relatively simple version control system so it works great for an individual or small team (less than 10 people). But if you have a medium to large team, especially one with members distributed over a large geographic area, or one where individuals need to be able to work "offline" without access to a central server, Apache Subversion will likely not be the best choice.

Also, if you're maintaining an open-source project where outside people will be interacting with your code repository, git is probably a better choice because it's becoming the de-facto standard these days and what most developers are familiar with.

Incentivized

The software is easy to use and share within our team. Licensing and setup is straightforward. The product just works and we love it.

Incentivized

In our small membership-based organization, we have many stakeholders both internally and externally. GoProof doesn't require accounts and is extremely user friendly. I find even the most technology-hesitant person is comfortable using GoProof. Many within my company take advantage of a flexible schedule, but that means reviewing marketing projects under deadlines can be tricky. GoProof can be easily accessed and proofs quickly reviewed. The system then notifies all stakeholders of updates so fewer emails need to be sent. It's much more efficient and I find work is completed much faster.

Incentivized

• Revision control done properly - you have end to end visibility of all changes in the project.
• Conflict resolution - visually highlighting the differences helps to track down the problem.
• Being open source and very popular.
• We are using SVN hosted in our network - it is very stable, we had almost zero downtime in 4 years.
• Rollbacks are made simple and easy to use.

Incentivized

• Customizable workflow steps help organize projects
• Time tracking down to seconds helps to estimate sprints
• Burndown charts let you know when to plan your next release

Incentivized

• Reviewing design proofs
• Easy for new users to understand
• Commenting history
• Integration with Adobe CC

Incentivized

• Distributed development - I've never worked in an environment where distributed development (developers widely scattered geographically) was a factor, but that's why git exists.
• Merging - Merging of code from one branch to another can be painful, especially if it's not done frequently. (On the other hand, doing merges is one of the reasons I get a nice salary, so I can't complain too much!)
• Acceptance - Let's face it, git is what "all the cool kids are using." If you've got a bunch of developers fresh out of school, they'll probably know git and not Subversion.

Incentivized

• Timing Out - when editing a story or bug, occasionally Axosoft will time out and all changes will be lost
• Viewing past sprints can be hard to locate
• Multiple users within a Story - Axosoft could do a better job managing multiple users on the same story
• User Interface isn't entirely user friendly and looks a bit outdated

Incentivized

• Reviewing design and function of email and web pages
• Adobe CC extension occasionally won't load
• More agile foldering/organizing system

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.

Over the years, I have used many Git tools, but GitKraken stands out. It's now my favorite Git tool by far—excellent graphical overview of the branches, straightforward usage of all functionality, and lots of integration available. Currently, I am using GitKraken to connect to the ADO and quickly create PRs, using gitflow and tracking the work of my team mates.

Incentivized

Git has become the new standard of version control, with its support for distributed design. As a tool to manage and control versions, Subversion does it well, but Git is the future.

Incentivized

I actually like JIRA better, to me the UI is a lot cleaner. Easier to use, and search tickets.

Incentivized

I prefer GoProof over PageProof. GoProof has a more user-friendly layout and workflow. PageProof has many functions hidden on the screen so it's not as simple to understand. One of the features, in particular, adding other reviewers, is too complicated with PageProof and I am never sure if I am doing it correctly. GoProof allows proofs to be removed by an administrator no matter the status of the creator. With PageProof, I have proofs sitting in my inbox for months that were unfinished for a reason but I can't remove them. PageProof does allow emails and webpage to be sent through the system to review function and design. It's a really great feature that I wish GoProof had.

Incentivized

• Subversion helps us feel secure in maintaining access to all of our product code, both current and historical.
• Being free and open source makes it an even better "investment".

Incentivized

• Productivity bump for developers over previous software
• Code is never gone forever and can be found if needed
• Allows us to collaborate and finish projects faster

Incentivized

• Went completely paperless and sold two large printers
• Flexible employee schedules no longer hinders project flow
• Work from home is possible and very easy

Incentivized