The main reason is that mercurial doesn't handle well sub project in a
single repo. Mercurial is really meant for one package = at least one
repo (most of the time multiple repos or branches per package ). For
example there is no way to partially checkout a mercurial repo.
that leads to a lot of repos since we have a lot of "packages" (each
application, each content_object, each external repository driver, each
video conferencing driver) but unfortunately google only provides 10
repos max for a project and therefore we would need more than 7 google
projects...
Bitbucket has a smarter way of handling a bigger number of related repos.
This the big picture of the why but if someone sees something I miss,
feel free to add it ^^
We can discuss the reasons behind that move friday, too.
Systho
Le 15/02/2011 21:17, Yannick Warnier a écrit :
Hi everyone,
as most of you know, Chamilo 2 is changing its Version Control Host and
is also defining a package policy.
Hi,
I didn't know about that but would be interested in the train of
thoughts that led to the decision (is that based on these discussions
about having branches for dev and stable versions and stuff?).
IRC log, anyone?
Yannick
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
