PUBLIC MARKS with tag versioning

Git is a free & open source, distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Every Git clone is a full-fledged repository with complete history and full revision tracking capabilities, not dependent on network access or a central server. Branching and merging are fast and easy to do.

Software version numbers should be straightforward to implement. Their sequencing is hardly subtle: version 1.0 is the first production quality release; version 1.1 improves on it, version 1.2 is a little better; and so on until we get to version 2.0, which delivers more substantial changes. Then comes 2.1, then 2.2 ...

As anyone who has tried to implement such a scheme will realise, it can be a surprising source of problems, and although these problems have been tackled by many projects in many organisations there seems to be no consensus on how to reach a solution. To give an example: deriving the version number from the version control system is tempting, but ultimately turns out to be unsatisfactory.

Flashbake automatically embeds ambient information in each version of those files—like the weather, your Twitter status, the last track you listened to—by including it all in each version's commit message.

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.

Pitz is (going to be) yet another bugtracking system, with these goals:

Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like git, darcs, Mercurial, and Bazaar. It can also be used with centralized systems like SVN.