Recently the PHP project announced a move to git as the primary version control system for the language's development. In a new post to SitePoint's PHPMaster.com site, Davey Shafik explains what that means to the average developer and what you can expect of the future.
Just over two years since its move from the antiquated CVS to Subversion (SVN), PHP is once again on the move: this time, to Git. Well, eventually. The migration from CVS to SVN was a huge one and took many months. The need for the PHP project to support its user base, hook scripts (commit mailing list, etc.) means that any change of revision control software means quite a large commitment. This is why even though the voting is over, and the dust has settled, we won't be seeing PHP on Git until the end of this year.
Davey shares his vote - pro-git - and explains what his choice (and many others') means for the language, including a modified patch acceptance policy and a convenience for developers to be able to work anywhere.
All in all, I feel migrating from Subversion to Git can only be a good thing for the PHP project and the community as a whole. [...] it is pretty clear that the PHP development community is in favor of the decision.