Generally looks good. >>>>> "Mark" == Mark J Nelson <Mark.J.Nelson at sun.com> writes:
Mark> My plan is to send this note once a week until we get to build Mark> snv_95, and then send it more frequently. Once a week seems a little too often, at least to start. Maybe start out once every 2 weeks, and move to once a week at snv_94? Either way, you'll want to call out changes whenever there is an update to the text. Otherwise, people will read the first couple lines and then delete. Mark> - The /ws/onnv-gate will transition to Mercurial for build 97. So the initial Mercurial gate will still be called /ws/onnv-gate? I'm not sure that's what we want to do, for a variety of reasons. It means figuring out the NFS exports: will everything be exported read-write, or what? And it's not how the gate will be deployed when it's external. Plus there's the whole performance issue we've run into with NFS. It might be better to use ssh access to the gate. If we do continue allowing NFS access, we'll need to allow for NIS updates to the auto_ws map when the switch happens. Mark> ------ Developer Responsibilities, aka What You Need To Do NOW ------ I agree with Bill's comment about encouraging people to try out wx2hg. I would particularly recommend this for workspaces with a likely putback after the transition date. They could also start poking through our transition documentation. Mark> When the tools integrate (don't worry, we'll send out a flag Mark> day messagae), Typo: messagae -> message Mark> We'll keep you posted when we integrate the tools, and provide Mark> more details on how to have be happy and productive in a Mark> Mercurial world. "how to have be" -> "how to be" mike
