I don't think you need to create another branch for openacs.org. You could just run openacs.org directly from OpenACS-STABLE. This is what I mean:
1. HEAD always has the latest development sources. It's considered unstable and fit only for innovations and major work. This would be OpenACS-CURRENT.
2. As we approach a release, HEAD stabilizes (feature freeze) until the release engineers think it's stable enough to make a release. When the release is made, HEAD is branched as a .0 release (OpenACS-4) and a symbolic tag is made for the actual release (OpenACS-4.0). The new branch will be the stable branch.
3. openacs.org can be run directly from the stable branch. Bugfixes in the stable branch (and thus in openacs.org) are integrated with HEAD.
People who want to stay "Current" with OpenACS will just follow HEAD.
People who need stability will just follow the latest STABLE branch.
openacs.org could periodically sync with the STABLE branch.
This is more or less how the FreeBSD project manages their OS. I think it's a good methodology.
Regards,
-Oscar
