Oops, forgot to cc the team. Tomorrow I need to get the wx2hg output fixed to get rid of the older-than-one-day warning and the /ws/onnv-clone text. (Unless one of you wants to take that bug.)
And either I or somebody (Mike?) will need to get Mike's updates into the gate README, including (I hope) the corrected nis map entries that I sent this evening. I'll be checking tonight's list of approved RTIs, and ramping up invitations in the morning. Whether or not we open it up tomorrow is completely dependent on how that goes, but Dave and I are cautiously optimistic. --Mark ---------- Forwarded message ---------- Date: Thu, 07 Aug 2008 22:41:23 -0600 From: Mark J. Nelson <mark.j.nel...@sun.com> To: on-discuss at opensolaris.org Subject: Mercurial transition status: 21:40 PDT Thursday, August 7 We trickled a few more pushes into the gate today, and are still fine tuning the back end of this whole process. Dave Marker now knows WAY more than he ever wanted to about the fascinating combinations of Python, environments, user ids, ssh, Mercurial, file ownership, permissions, and trust. So far we've been kicking off some of our "periodic" jobs (like the clone update and nightly build) manually. We still need to let 'em run in their natural (aka cron) environment, but we're pretty comfortable with their correctness. The process of pushing a changegroup is still taking longer than we want, and we'll be working on that for the next few weeks. But we're about to shift some of the burden onto all of you: tomorrow we start hammering this thing, and if you want to be part of it, you need to have done your homework. Look back over my notes for the last few days. Get familiar with merging. In case you haven't realized it yet, I'll spell it out: you're going to need to pull from the clone, merge, and recommit before almost every push. And if you're NOT validating the results of each merge (using webrev or hg diff or whatever you're most comfortable with), then you're running with scissors. Don't do that. On a philosophical note: there is no subtitute for learning. You can't go straight from "Teamware power user" to "Mercurial power user" without passing "go." And we can't take you there, either. You've got to do it yourself. If you're relying on a cheat sheet, you're not there yet. We can hold your hand for a little while, but frankly, that's boring and it's not our job. So learn this stuff. Don't send us e-mail and call us every time you're not sure what to do next--figure it out yourself. Then, when you really do get stumped, we can actually have an intelligent conversation, because you'll know enough to ask the right questions, and we'll recognize the effort you're making and answer you with something more than "go read the information we provided." When you find stuff that we've gotten wrong, or forgotten to tell you, please let us know. We really do want to provide y'all with the tools and information you need to be successful, but sometimes we forget how confusing the basics can be when you're learning. As always, thank you for your patience. --Mark
