Darren Reed writes: > It might be useful for the SCM team to keep around a teamware > gate for people to putback into that have been using teamware > for some time. We need to move forward, but ... requiring > projects to change SCM just to do putback seems....
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. There've been a couple of TOIs given for Mercurial usage, and there will likely be more. There's no plan to have a Teamware gate available for putback once the transition occurs. Doing so would require bi-directional gateways, which we've looked at and decided were riskier for all involved than a straightforward transition. As for using the tools, you should be using them now. OpenSolaris (aren't we working on that?) uses Mercurial and CVS, not Teamware. The main build servers in Burlington use the new tools, and have been for some time now. It'd be very helpful if someone out in Menlo could configure some of the build servers there with the new tools. Any volunteers? (I never use those systems, so I don't know where they are, let alone who maintains them.) -- 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
