Darren Reed writes: > James Carlson wrote: > >No matter when we do the transition, there will _necessarily_ be > >projects still in flight. The smart ones will transition early in > >order to minimize their pain and risk of surprise late in the game. > > > > > > I think the best that can be asked for is a heads-up a week > or so in advance of the putback so that we don't have project > teams arriving at work the day before they were going to do > their putback and find out they now need to do hg.
You have been and will continue to get much more notice than that. We've discussed this publicly several times now. First, there'll be a putback of the updated tools. You'll be able to transition your long-running projects over to Mercurial fairly effectively then. (Of course, you're able to do that now, as long as you use the pre-release tools available on the web site and on some common build servers.) Then there'll be the transition of SFW to Mercurial. I'd expect this to follow the usual sort of process: an announcement to the gatelings of the impending change in a future build. "Future build" necessarily means that there'll be at least two weeks of notice, and likely more. And then comes ON. Again, there'll be a heads-up announcement of the usual sort that you see when there are "restricted" builds or other gate schedule changes. I expect the transition to occur within an identified bi-weekly build. As for timing, I'd expect the tools putback to occur within a few weeks. We're wrapping up our internal code review now, and external is next. The SFW transition is shortly after that. The ON transition follows with a few weeks of delay so we can shake down whatever problems may have happened in SFW. (The ballpark figure I've heard is mid-August, but don't hold me to it now; I'm not even the lead.) If project teams can't plan their projects around that, then I think they'll need to work with their managers and/or gatekeepers to figure out what to do. For what it's worth, if I were working on a large project now (and I am), I'd use Mercurial rather than Teamware. Besides being a bit better to work with, the downside of finishing early and having to decide between porting the diffs to Teamware or waiting for the transition is less than continuing on cruise control in Teamware and discovering at the last minute (due to inattention) that it's gone. I'd rather be relaxed than hasty. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
