I talked to Mike Sullivan about migrating SFW before ON, and he is pretty adamant (understandably so) about wanting our tools integrated into ON first so that he doesn't have to install a private SUNWonbld package, especially given SFW's developer's shared use between SFW & ON workspaces and potentially shared build machines.
So basically the scenario he is envisioning is: 1) we putback our changes making sure they still work for Teamware since ON will still be on Teamware (excepting the SCCS keyword cleanup, and possibly other changes) 2) convert SFW to Mercurial 3) convert ON to Mercurial later What do you guys think? It's not the answer I was hoping for, since I was hoping SFW would provide some exposure/testing to the tools before they went into ON; but I can understand Mike's concern. Honestly I think if this *did* happen, it would just push back the migration of ON, since I don't know that we'll finish up all our work by September to integrate into ON anyway. On the plus side it does make sure that our tools are backwards compatible (not that I think that's really an issue), and it will get us additional tools testing as people will really start using the tools on mercurial workspaces (since not everybody knows how to find our onnv-scm SUNWonbld) cheers, steve -- stephen lau // stevel at sun.com | 650.786.0845 | http://whacked.net opensolaris // solaris kernel development
