Archives for the tag: code review

I've been doing a bit of traveling lately on the second leg of the Getting Git Right tour. It's been a blast meeting so many devs from around the world. It's been particularly incredible to see how much git adoption has grown amongst attendees in the few months since we did the first leg of the tour. When we presented in July, almost all attendees raised their hand when we asked "Who's using git?".
However, there is one low point during every evening that I've hosted: the moment after I ask the

Developing software often involves teams of people working together. As the team grows from one, to two, to multiple people, challenges begin to creep in and rob the organization of creative flow. It becomes harder to maintain a continuous culture across different people. Engineering groups are especially prone to these challenges as code is routinely shared between many people throughout the organization. Code reviews help spread knowledge and best practices around code across the team. In this

I'm thrilled to announce the release of FishEye and Crucible 3.3! Reviews are now easier to process and you can extend the integration with your systems with new REST resources. On top of that, FishEye and Crucible are now a step ahead in supporting new technologies of the latest Subversion and Internet Explorer compatibilities.
Try FishEye and Crucible 3.3 today
Stay on top of your priorities with the new review header
We redesigned the review header to bring you a better experience during

One question that every team faces when moving to Git is what development workflow to use. Since every team is different and has different requirements, there is no one-workflow-fits-all approach. However, there is one rule all teams should follow when looking for a new workflow to adopt: Keep it simple. Doing so will reduce the number of mistakes people can make, and will help with adoption.
On the Stash team, we've adopted one of the simplest Git workflows possible. And since so many of you

Security versus usability: This is a tradeoff we're all familiar with in software development, and even applies to hosting your code. Part of the challenge of enterprise-grade repository management is the ability to keep your intellectual property secure, while safely exposing the public-facing parts of your code to the people who need to access it.
Recently we've given more flexibility and granularity in the way that your code is exposed: 2.0 introduced the ability to protect certain branches