> It is further concluded that the Subversion module will be empty, > and for our 'playing pleasure' until a un-determined date in the > future, when the content is populated from the CVS.
The test repository was setup many months ago. The real question is when you want Fitz to migrate data. An e-mail I saw indicates some fundamental misunderstanding of how Subversion works. There is no "Avalon module", nor is there a directory or UNIX group associated with it. The ASF maintains a test repository and a main ASF repository. All of the live code is in the latter. You can see this using http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN. > No committers objected to a manual transition of the content, > where history will be lost. I object and I object strenuously to the loss of history. There is no need for it. The existing CVS modules can be migrated into SVN at any time. Aaron, the Avalon Subversion permissions are currently configured as: [/avalon] @avalon = rw [/avalon/components] @james = rw @cocoon = rw [/avalon/sandbox] @james = rw @cocoon = rw which means that Avalon has read-write to everything under that tree, and there are two other portions of the tree that are also read-write for James and Cocoon. All of the avalon-X products would migrate as /avalon/X, so you can see how that would fit together. I assume that meets with everyone's approval. FWIW, it would have happened this weekend, except for what were perceived as mixed signals. --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
