monotone support

[anonymous]

Considering 2.0 enhancements it would be great to support monotone ​http://venge.net/monotone/ SCM system. It grows very fast and was considered by Linus Torvalds to replace BitKeeper, in fact git (a fast written Linus's tool to manage Linux sources w/o any SCM) was desinged based strictly on ideas behind monotone.

---

Development of a trac plugin for connecting to a monotone repo has been started, see ​http://www.ipd.uni-karlsruhe.de/~moschny/TracMonotone

This ticket can be used to discuss the additional requirements for the version control layer that would be needed for improving the support for Monotone.

If I remember correctly, this is mainly:

• support for full, normal and shortened revision numbers
• support for multiple branches/repositories (related to #2086)

[anonymous]

See also the Darcs support patch in ticket #638. It contains a generic SCM backend interface that the Monotone support probably could implement.

[Christian Boos]

Well, no: There's an official generic SCM backend interface currently in current development version of Trac, and this is the one to implement. See source:trunk/trac/versioncontrol/main.py#latest

[Christian Boos]

s/currently sorry :)

[njs@…]

As current head cat-herder/developer behind monotone, I thought I'd put in a word here… I'm definitely interested in seeing this happen (it'd be nice to use trac for monotone development itself!). I thought a bit about adding it myself, but simply don't have the time; but, if someone else decides to take a shot at it, we'd definitely be interested in helping provide info, fixing interfaces to be more usable, etc.

Monotone might be an interesting target in any case, since it's one of the most different VCSes from subversion — unlike subversion it has first-class branches and tags (so a monotone repo is not a simple singly-rooted tree), and unlike, say, darcs or arch or bzr-ng, it has microbranches (so even within a branch, history is a DAG, not a line). Looking at source:trunk/trac/versioncontrol/api.py#2127​ , the current API seems to assume that history is a straight line (e.g., that each revision has exactly one predecessor and successor); this simply isn't true for several of the new generation of VCS tools. So if you can support monotone, you can probably be pretty sure that your design can support anything :-).

[moschny]

Development of a trac plugin for connecting to a monotone repo has been started, see ​http://www.ipd.uni-karlsruhe.de/~moschny/TracMonotone/.

[Christian Boos]

I'm setting a milestone here for the improvements on the versioncontrol API and web interface, not for the plugin itself, of course.