Sloanspace is most definitely "based on" the dotLRN CVS, but it is not an identical copy. Same goes for OpenACS. We're all waiting for the day when you can build a site solely through configuration without the need for editing distribution files. Today that approach is impractical for Sloanspace. So for now we are importing OpenACS and dotLRN as CVS vendor branches (
this document describes how we do it). It is working quite well. We've merged 7 times now
symbolic names [for readme.txt]:
Production: 1.1.1.2
Staging: 1.1.1.2
Head_2002_08_19: 1.1.1.2
ReleaseBranch20020804: 1.1.1.2.0.2
Head_2002_08_06: 1.1.1.2
Head_2002_07_23: 1.1.1.2
Head_2002_07_15: 1.1.1.2
Head_2002_07_09: 1.1.1.1
Head_2002_06_25: 1.1.1.1
Head_2002_06_13: 1.1.1.1
dotLRN: 1.1.1
Each
Head represents a merge of the latest code. Or next merge will be against the 1.0 release.
How big is the diff? It's manageable, at least, or we wouldn't have been able to merge so many times. But this is a great question for Caroline to answer. What I can say is that it is very much in our interest to take merge the non-Sloanspace-specific improvements and bugfixes (here is a particularly cool bug) back into dotLRN. As I type, we are working with OpenACS team to do this for OpenACS. The smaller the diff, the happier we are.
