InDefero is a simple to use software forge. Save you and your team time and track bugs, provide downloads, documentation and have an easy overview of your code base.
Bugs Everywhere is a “distributed bugtracker”, designed to complement distributed revision control systems. By using distributed revision control as a backend for bug state, we gain several convenient features: * Bugs and code that live on branches are tracked together—when a branch is merged, both the code changes and bug changes that the branch contains are merged alongside each other. We no longer have to be confused about whether a fix that is applied to the development branch but not yet present in the production branch means that our bug is “fixed”. * Users can fully modify bug state while offline, unlike with many centralized bugtrackers. * When a user checks out your source code, she gets the current bug state for free. * We can still provide access to a friendly web interface for users—in this model, a web interface becomes just another client that merges with the main repository.
]]>
This document summarizes the initial research for adding distributed version control as an option for Google Code. Based on popularity, two distributed version control systems were considered: Git and Mercurial. This document describes the features of the two systems, and provides an overview of the work required to integrate them with Google Code.
]]>
]]>In contrast with my earlier attempts at migrating to git, mercurial was actually a joy to setup on the server. WSGI, using our existing .htusers file from Trac, a small config script, done. This contrast to git which would require some funky SSH sandboxing and/or PAM setup - yes it can be done, but such hacks shouldn't be needed.
To all our surprise "hg clone" was extremely fast even compared to subversion and especially in comparison to git.
]]>
"Git is MacGyver, Mercurial is James Bond" : it says it all :-)
Scott tells why you should switch to Git instead of any other version management system.
TortoiseHg is an all-inclusive Mercurial binary installer package for Windows, which provides a windows explorer extension (shell extension), so that Mercurial commands can be executed from the context menu of the explorer. Command line "hg" is included as well. No other packages are needed (for example, Python is already included as a dll). Includes several dialogs, for example for committing and history viewing/diffing. Also includes a MergeProgram and software for ssh server access.
]]>
]]>
Tailor is a tool to migrate or replicate changesets between ArX, Bazaar, Bazaar-NG, CVS, Codeville, Darcs, Git, Mercurial, Monotone, Subversion and Tla repositories.
Since Linus Torvalds presentation at Google about git in May 2007, the adoption and interest for Distributed Version Control Systems has been constantly rising. We will introduce the concept of Distributed Version Control, see when to use it, why it may be better than what you're currently using, and have a look at three actors in the area: git, Mercurial and Bazaar.
Since Linus Torvalds presentation at Google about git in May 2007, the adoption and interest for Distributed Version Control Systems has been constantly rising. We will introduce the concept of Distributed Version Control, see when to use it, why it may be better than what you're currently using, and have a look at three actors in the area: git, Mercurial and Bazaar.
A guide to three major Distributed Version Control Systems: git, Mercurial and Bazaar.
Although mercurial may still feel nicer today, the change feels inevitable. This flood of people leaving centralized systems means that it's way easier to contribute to their projects than ever before. This is the important part. In the end, we all wi
Bazaar, Hg (Mercurial) ou Git sont-ils les dignes successeurs de SVN et CVS ? C'est ce que Dave DRIBIN compare dans son blog.
]]>
]]>
]]>