Geir Magnusson Jr. wrote:
Clearly, we need something like this to get organized around the final push for certification and the 1.0 release, by why not just branch for the stable, and head is unstable?


The names are just suggestions - "trunk", "head", "unstable", whatever.

The important thing is that you can easily checkout and build each tree on its own so we can't have both stable and unstable branches of modules (e.g. transaction) under trunk.

--
Jeremy

Reply via email to