Our CVS is hosted at Sourceforge. Usage information is in Section F of their [http://sourceforge.net/docman/?group_id=1|documentation page]. If you like, take a look at our [/cvs|groovy stats]. And now, ++yellow: how Bitweaver CVS is organized:++
-Our CVS tree has one ++yellow: module++ for each package. However, a virtual module is use to create three primary distributions: __bitweaver__, __bitweaverdev__ and __bitweavercore__. Every ((bitweaverRoadMap|bitweaver release)) has a CVS ++yellow: branch++ named after it. The branch is created ''after'' we have gone into schema freeze for the project. For details on __how to get code__ (checkout modules, branches, packages) please refer to ((GetCode|this page: GetCode)).
+Our CVS tree has one ++yellow: module++ for each package. However, a virtual module is use to create three primary distributions: __bitweaver__, __bitweaverdev__ and __bitweavercore__. Every ((Roadmap|bitweaver release)) has a CVS ++yellow: branch++ named after it. The branch is created ''after'' we have gone into schema freeze for the project. For details on __how to get code__ (checkout modules, branches, packages) please refer to ((GetCode|this page: GetCode)).
! CVS Modules
@@ -23,6 +23,8 @@
! CVS Branches
* __R#__ - R1 is equivalent to Release 1 and symbolises a stable release branch that will not undergo any API changes or database schema changes.
* __ HEAD__ - no guarantees for stability provided. Might break at any time. There's no official support for this branch (still, you're welcome to ((ConnectingToIrc|join us on IRC)) if you have questions). Use this branch only if you are a developer.
+
+(__NOTE__: As of 2007-11-19, HEAD is considered stable as we have released ReleaseTwo, but have not yet created an R2 branch)
As discussed in ((ReleaseProcess)) there are three active branches in CVS: STABLE, TESTING, and DEVELOPMENT. See ((ReleaseProcess)) for which branch is currently in which state.