Currently .LRN is used for two different things. On the one hand the software package that should be an installation option of OpenACS, enabling us to have one release system, one project one community and one technical governance.
On the other hand we have the .LRN brand cum consortium. The brand is getting established in the area of higher learning and is therefore valuable and should not be demolished lightly. The consortium on the other hand is an entity of *users* that gives new adopters a good feeling that they are not making a mistake by choosing .LRN and gives them security that there is an entity coordinating the needs of the users.
Coming back to Tracy's comment about the two different release circles, I think we should make sure that we release the packages along with the core. All packages with a certain maturity level should be part of this release process and this should be reflected in an extra maturity level four which adds to three the point "has undergone the official release circle along with all release criteria".
