Recently [announced](https://github.com/blog/2131-git-2-8-has-been-released) Git 2.8 brings many new features, improvements, and bug fixes. Among the most noteworthy are parallel fetch for submodules, an improvement to how Git handles a user's identity, and better support for Windows.
GitLab 8.5 brings a host of new features and improvements, including a significant performance boost, especially when running very large instances; Todos, a new feature aimed to help keep track of pending tasks for developers; and GitLab Geo, only available for GitLab Enterprise Edition, that supports geo-replication to improve performance for geographically distributed teams.
GitHub introduced a new, highly requested feature that will allow project maintainers to define custom templates for issues and pull requests. Additionally, GitHub’s web UI now supports the possibility of uploading files.
Two months after the release of version 2.6, Git 2.7 has been announced, bringing many new features as well as performance improvements.
Many teams now implicitly discard continuous integration due to ever-easier feature branching and an under-appreciation of trunk based development says Steve Smith. InfoQ did an interview with him about different branching approaches and how they can be combined with continuous integration, and how using build feature branching can hamper continuous integration and continuous delivery.
Git 2.5 is a major feature release that includes worktrees, improved triangular workflows, better performance, and countless improvements and fixes.
Open Source project hosting sites like SourceForge, Codehaus and Google Code inspired developers to share their code for projects not associated with a foundation like Apache or Eclipse. Over the past few years, these hosting sites have been superseded by GitHub, to the extent that they are closing down over the next year. InfoQ looks back at their contributions and into the future.
Atlassian's popular source code hosting site Bitbucket launched Snippets for teams, a collaboration oriented solution to "create and manage multi-file snippets of all kinds". Snippets can be created via drag and drop, owned by a user or a team and optionally shared publicly. They are backed by Git or Mercurial repositories and can be managed via a REST API.
A critical security vulnerability affecting Git and Mercurial has been announced yesterday, making it possible for an attacker to execute arbitrary commands in the client machine. The vulnerability only affects clients running on OS X (HFS+) and Windows (NTFS, FAT). The Git core team has published new releases for all current versions of Git.
JetBrains has made available Upsource 1.0, a source code collaboration tool for software development teams.
The database source control and deployment system DBmaestro now offers SQL Server support. This tool, which is also available for Oracle, is designed to be used in environments where multiple instances of a database exist in development, QA, and staging branches that need to be kept in sync with source code changes.
Today, Greg Stein, founder of the Apache Subversion project, raised a request to migrate the Subversion codebase to Git. More controversial than the decision itself was the way that the decision was made, by the PMC on the private mailing list. Read on to find out what happened and what the current state is.
Facebook has posted on how they've sped up Mercurial to be five times faster than Git in certain operations. Read on to find out what they have changed, and why it makes such a difference for their setup.
Versioning of services is something which has been a cornerstone problem of SOA. There are many examples over the years of experiences gained and shared, but little in the way of concretely comparing and contrasting different approaches. Jean-Jacques Dubray has written about the experiences of his team in this area and some equations they have developed to try to illustrate the differences.
"Don't version unless you absolutely must, and it is rare that you absolutely must" says Mike Amundsen in a series of API design workshops he held recently. Amundsen describes the "USE" paradigm for API design focussing on usability, scalability and evolvability. He describes the three most common styles of API implementation and how they compare to these principles.