dolfin team mailing list archive

[Johan Jansson <jjan@xxxxxxxxxxx>]

We had an idea to create a branch of DOLFIN where we could work on
(and break) the mesh while still keeping a more stable DOLFIN branch
with the old mesh. Now it turned out the other way around, the mesh
was replaced in the main DOLFIN branch while the new branch was kept
stable. Anyway, I think it has worked rather well to have two
branches, high-level development has been able to continue in the
stable branch, and kernel development has been done in the main
development branch.

Notifications from the stable branch (called "dolfin-kth") have not
been sent to this list though. I've turned that on now. There have
only been a few changesets, you can view them here:

http://www.fenics.org/hg/dolfin-kth

Please comment if you have ideas how to organize the branches, if we
should have two branches inside the same repository (doesn't work so
smoothly with Mercurial in my experience), or whether we should have
separate repositories (even more than two perhaps).

Starting/cloning a repository is so simple in Mercurial (everyone has
a private repository anyway when they develop), so I think it's
natural that every repository represents a branch.

  Johan