Standard apology for folks on lots of e-mail lists...
Howdy, Sun and OpenSolaris ON Developers-- You've been hearing about this for a while now, so there shouldn't be any surprises here, other than the specific dates. The ON gate for build 96 will close at 23:00 Pacific Time on Monday, August 4. When it reopens for build 97, it will be managed using Mercurial. The timing for this gate opening is not yet known: it might be immediate, it might be overnight, or it might take a couple of days. But that's not really important right now: it will be managed using Mercurial. Because "migration" tends to confuse folks, we're calling this the "transition" to Mercurial. Later we'll "move" the ON gate off of SWAN and onto opensolaris.org, but that's not this note, it's just clarifying the terms. ------ Project Status, aka This Really Is Happening ------ - The necessary changes to the SUNWonbld developer tools are currently under review, and expected to integrate to /ws/onnv-gate the week of Monday, June 23. - The SFW Nevada Gate will transition to Mercurial at some point in time following the integration of the SUNWonbld tools, exact timing TBD, but intended to precede ON. - The necessary changes to ON gatekeeper tools are in progress. - The ON Nevada Gate will transition to Mercurial for build 97. ------ Documentation links, aka Learning Opportunities ------ Steve's KTD slides: http://ktd.eng/mercurial.pdf Our project page: http://www.opensolaris.org/os/project/scm-migration/ ...and more to come, but there's enough here to get you started if you're curious. ------ Developer Responsibilities, aka What You Need To Do NOW ------ 1. Start using the Mercurial-enabled SUNWonbld tools to manage your Teamware workspaces. If you use the Burlington public build servers, zhadum and trigati, you're already doing this. Otherwise, you can download them from the SCM Migration project page: http://www.opensolaris.org/os/project/scm-migration/ ...or wait for us to integrate them, and get them "automatically" when you keep your build machines up to date with SUNWonbld flag days. That last part (keep your build machines up to date) will be particularly important for folks that are already using Mercurial. When the tools integrate (don't worry, we'll send out a flag day message), you'll need to say goodbye to your custom tools and get on board the SUNWonbld bandwagon. Using these tools is not the same as using Mercurial. The tools have been enhanced to work with multiple SCM systems. You can continue working in TeamWare for now, and still use the new tools. 2. For bonus points, read the Mercurial book: http://hgbook.red-bean.com/ ...this is particularly useful (required reading?) if you're accustomed to peeking under the hood (ie using SCCS or manipulating the nametable) in TeamWare. This tool is much different, and you should not expect to bypass it, or muck about with the way it stores files. 3. That's about it. Keep sniffing the air around you--that's the scent of change, and it's coming. We'll keep you posted when we integrate the tools, and provide more details on how to be happy and productive in a Mercurial world. ------ Developer Preview, aka What Might Be Fun To Do Next Week ------ Go to the scm-migration project page on opensolaris.org, download the tools, and convert a workspace using wx2hg. Experience the wonder of the working directory, as opposed to managing all of those files individually!
