External folks: though the specific paths and nfs details won't be all that interesting, the gate/clone arrangement is something that I expect to be preserved when the Mercurial gate is moved off-SWAN.
Flag day: On Tuesday, August 5, with the transition to Mercurial, the gate and clone arrangements will change significantly. In this note, any unqualified reference to "gate" (or "clone") refers to the Mercurial gate (or clone). Details: - The gate will be write-only. You will push to the gate via ssh, using a shared account setup for this purpose. Details of that ssh access will be described in a separate note. - Over nfs, you will have read-only access to the working directory of the gate, but not to the .hg directory. That means that you'll be able to browse the code, but even over nfs, you will not be able to do Mercurial read operations from the gate. - Each changegroup pushed to the gate will be immediately synced to the clone, and to the external (hg.opensolaris.org) gate. - The clone will be read-only. You may pull from the clone via either nfs or ssh. For anonymous (scripted) access, you may use nfs, but you should create your initial repository via ssh for better performance. - We plan to provide an empty-passphrase, restricted access ssh user for anonymous, ssh-based access, but it's unclear that will be ready in time for tomorrow's conversion, so we'll send a separate note about that when it's ready. - The clone will now be updated in real time. Builds, however, will continue to be done on a nightly basis. When a nightly build is kicked off, the clone will be given a local tag named "nightly," so you can always do "hg pull -r nightly" from the clone if you want to be in sync with the most recent nightly build on the gate. - The old Teamware gate and Teamware clone will still be available, though not via the same paths. They will NOT continue to be updated beyond Monday night. - The Teamware clone will continue to be an appropriate parent workspace for workspace conversion using wx2hg. --Mark
