GitHub just added a new feature: files in the web view of a Git repository can now be edited and then committed in the browser. A similar feature was added to Google Code a few months ago.
Veracity is a DVCS that can be installed on Windows, Mac, and Linux, and uses a distributed database for its repository.
Google Code has finally released support for Git repositories on Google Code, adding to the existing DVCS support with Mercurial and the CVCS support of Subversion. The only remaining player not to fully move towards Git repositories is now Apache, which has its own read-only copies of a writable Subversion repository.
GitHub have launched a desktop client for Mac OS X called simply GitHub for Mac.
GitHub recently announced they had passed two million git repositories hosted, with 70% being created in the last year alone and an expected 1m users later this year. What else is new at GitHub?
First Haskell, and now Eclipse moves to GitHub. Only Git repositories are being mirrored to GitHub, but there's more than 70 repositories already created at the Eclipse Foundation page on GitHub. With EGit 0.11 being released as part of 3.6.2 and aiming for a 1.0 release in Eclipse 3.7, there's more demand than ever to move to Git for Eclipse projects.
The well-known Haskell implementation GHC is moving from Darcs to a repository on GitHub, citing wider tool support and faster operations.
Since Microsoft announced that it was giving up control of its Iron languages, there has been a quiet debate on where to host the project. The negotiations have finally been settled and the winner is Github for source control and CodePlex for issue tracking.
Many .NET developers have turned to distributed source control systems. The most popular one seems to be Git, which was originally created by Linus Torvalds for Linux kernel development. One problem with Git is that it is predominately command-line based while .NET developers prefer to stay in the IDE. This is why Sun Yiyi’s Git Source Control Provider an important part of Git adoption.
The EGit and JGit Eclipse projects released 0.8.1 of their namesake projects earlier this week, in preparation for the Eclipse Helios simultaneous release that is due later this month. The New and Noteworthy for both EGit and JGit have been brought up to date, and a User Guide based on contributions from the Eclipse Wiki. There's also an Introduction to Git for those who haven't used it before.
Last week, EclipseCon 2010 (in conjunction with OSGi DevCon 2010) was held in the Santa Clara Convention Centre. This year saw a number of Eclipse-related technologies and tutorials; so, what was the key take aways?
With a recent announcement from Nick Quaranto, RubyGems.org has become the default gem source for RubyGems. The three domains gemcutter.org, gems.rubyforge.org, and rubygems.org now all point to the same place, and gem serving and installation work for all three. RubyGems.org is the main web front end, to which the other two sites redirect. The secure site, https://rubygems.org, is also now live.
The first public version of the org.eclipse EGit plug-in version 0.7.1 has been released at EclipseCon. EGit is based on the pure Java implementation JGit, which means that it has no external dependencies or native code requirements; something which has historically hindered the adoption of Eclipse's Subversion support.
Martin Fowler has conducted a survey on ThoughtWorks’ software development mailing list to determine how some of the version control systems (VCS) are perceived by developers. He also wrote a review of most prominent VCSes comparing centralized and distributed systems.
Since the last Bundle.update, a new milestone of NetBeans adds support for embedding OSGi bundles, and this week's London OSGi DevCon promises to be of interest. ECF 3.2 has been released, and EGit/JGit is making strong headway in the world of DVCS.