I hate to sound like a broken record, but: in preparation for moving the onnv-gate off SWAN, we're switching to using Mercurial as our source code management system. This note is the first of several bits of useful information that you'll see this evening and over the next couple of days.
Because this is an internal transition, much of the information won't be all that interesting to external folks. Feel free to skim or skip as you desire. Build snv_97 is an open build for all consolidations. As such, ON content will NOT be restricted. Any carefully tested, appropriately reviewed, approved fix will be allowed. That said, there will some differences for this build: - The onnv_97 gate will *NOT* open immediately after onnv_96 closes. Instead, there will be a delay of 12-24 hours while we change filesystems and mountpoints and such. - After 23:00 PDT on Monday, August 4, you should never again have reason to login to the onnv gate machine. Without an explicit invitation from the gatekeepers, anything you do there is suspect, and may be terminated. So ask first. Exception: xVM folks will continue with their current practices. - Beginning on Tuesday, August 5, we will begin taking integrations to the new, Mercurial gate. The first few such integrations will be by invitation of the gatekeepers, and will be coordinated to ensure that everything on the gate and build machines is working as expected. So if you see notification e-mail, it does NOT mean that the gate is open, or that it's OK for you to integrate. We'll announce it when we're ready. - The initial onnv_96 snapshot gate will be a Teamware workspace. If we need to respin the build, it will be done in a Mercurial repository. In other words, ALL integrations after 23:00 PDT Monday, August 4 must be done via Mercurial. - If you have an approved RTI based on a Teamware workspace, and you do not integrate before onnv_96 closes, you are responsible for converting your workspace. If you want your CRT advocate to review that conversion, you must explicitly resubmit your RTI. - If you are Contributing or Sponsoring changes, please (re)read the Sponsor Tasks page [1], as some of the information there has changed. In particular, Sponsors may now push changesets committed by Contributors, thus preserving author information and obviating the need for special "Contributed by" changeset comments. Questions to scm-migration-dev at opensolaris.org. --Mark [1] http://opensolaris.org/os/community/on/crt/sponsor-tasks/
