Recs.
Updated
Fossil goes beyond revision control and adds some basic source control management (distributed bug tracking, wiki, blog). It is transactional and aimed at ease of use. It was created by the author of SQLite and consists of a single executable.
SpecsUpdate
Pros
Pro Secure yet forgiving
Fossil is secure: by design, it never forgets anything. This pilosophy makes it very difficult to mess up a repository, or lose data, by making a false maneuver.
At the same time, Fossil does recognize that people do sometimes make mistakes. For example, it is possible to amend a commit message (much) later on. It is also possible to change a revision’s branch after the fact.
Pro Multiple checkouts from one repo
One fossil repository can have multiple checkout trees on the same machine, each for a different version. This can be used to support staging, and for quick fixes on older versions without disrupting the current development process. No need to duplicate the repo for that.
Cons
Recommendations
Comments
Flagged Pros + Cons
Pro Very easy to configure as self-hosted.
Single, stand-alone executable, including web server.