The Blender development infrastructure has been updated for the start of the Blender 2.7x release cycle. For a bird’s-eye view of the development process and infrastructure, and for how to get involved, see the new blender.org development page.
We finally switched from Subversion to Git for our source code repositories. The majority of development was already happening in Git, with many developers working with Git branches and repositories locally, so it only made sense to do it for our main repository as well.
We will eventually also set up mirrors of these repositories on websites like Github and Gitorious. If you are a developer, see the Git Usage documentation, for users making own builds, see the Building Blender for how to switch.
Bug tracking, code review, code auditing and repository browsing have all been moved to the new developer.blender.org portal, based on Phabricator. Previously we had development infrastructure spread over multiple websites. We hope that having functionality like code review closely integrated will make it easier to grow the project and accept more code contributions, while doing more review among existing developers to improve code quality and reduce bugs.
The new website should also reflect the actual project organization better. While most of the work is done in a single code repository, we organize ourselves in module teams. We now have projects for these teams, where the project page shows information about who is a member of the team, how to get in contact, and functionality for developers to add to do and design tasks for that project.
Thanks to everyone who helped with the migration, and for your patience while we were figuring out the details to get it all up and running properly!